<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Pending a final green sanity result,
the tentative restructure day will be Sept 4 (tomorrow).</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Please freeze ALL code submissions,
starting at 1 pm UTC on Sept 4, until further notice.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">I'll be running a repo split tool. It
will generate more than a dozen code reviews that will ALL have to
be merged before we can unfreeze the code for general updates.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">After everything has merged, you'll
need to ...<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">1) If you are working on code that has
not been relocated (refer to spreadsheet [3]) then 'repo sync
--force-sync' be sufficient. Before doing that, be sure to save
your work as a commit on a private working branch. <br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">2) If your working on code that has
been relocated, Then your best bet is to start with a fresh 'repo
init' into a new working directory. Use 'git format-patch' or
'diff' to capture your work, and apply the patch at the new
location. Some surgery to path names may be required. <br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Scott Little<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 2019-08-30 4:09 p.m., Scott Little
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:8b8d87c3-495d-0267-14b8-dfee39b8955f@windriver.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>The layered build feature is getting ready for its initial
required changes [1] [2]. </p>
<p>The first phase is a restructuring of the StarlingX git repos
to enable layered builds in the next phase. In light of new
package additions in the last few weeks, there has been a few
modifications and additions to the spreadsheet [3] documenting
all the intended moves. Edits are in <font color="#3333ff">blue</font>
text. The intent is that all package relocations will be
history preserving.</p>
<p>We plan to implement the git restructuring on the week of
September 3-6.</p>
<p>My initial ask of the StarlingX community is that we <b>temporarily
freeze the addition of any new packages</b> while we make a
final test run. This means that any updates that touch a
centos_pkgs_dir file should not receive a WF+1 until the
relocation is complete. After the relocation, you may need to
re-issue your code review. </p>
<p>Thanks for your co-operation.</p>
<p>Scott Little</p>
<p>[1] <a href="https://review.opendev.org/#/c/672288/"
moz-do-not-send="true">https://review.opendev.org/#/c/672288/</a></p>
<p>[2] <a
href="https://storyboard.openstack.org/#!/story/2006166"
moz-do-not-send="true">https://storyboard.openstack.org/#!/story/2006166</a></p>
[3] <a
href="https://docs.google.com/spreadsheets/d/1zURL1UlDST8lnvw3dMlNWN6pkLX6EVF6TDBwNR9TQik/edit#gid=1697053891"
moz-do-not-send="true">https://docs.google.com/spreadsheets/d/1zURL1UlDST8lnvw3dMlNWN6pkLX6EVF6TDBwNR9TQik/edit#gid=1697053891</a>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Starlingx-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Starlingx-discuss@lists.starlingx.io">Starlingx-discuss@lists.starlingx.io</a>
<a class="moz-txt-link-freetext" href="http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss">http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>