<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html;
      charset=windows-1252">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Al is fixing up some missing
      .gitreviews on the new repos.  We should be able to get reviews
      passed zuul shortly.</div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">Thanks Al.</div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">Scott<br>
    </div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">On 2019-09-09 9:53 a.m., Scott Little
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:333c1813-9ff8-d6a8-ef16-6fc862b79225@windriver.com">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <div class="moz-cite-prefix">We have a green sanity.</div>
      <div class="moz-cite-prefix"><br>
      </div>
      <div class="moz-cite-prefix">The freeze is now lifted. <br>
      </div>
      <div class="moz-cite-prefix"><br>
      </div>
      <div class="moz-cite-prefix">There is a spreadsheet [1] that maps
        the location of packages from old to new.<br>
      </div>
      <div class="moz-cite-prefix"><br>
      </div>
      <div class="moz-cite-prefix">Scott</div>
      <div class="moz-cite-prefix"><br>
      </div>
      <div class="moz-cite-prefix">[1]
        <a class="moz-txt-link-freetext"
href="https://docs.google.com/spreadsheets/d/1zURL1UlDST8lnvw3dMlNWN6pkLX6EVF6TDBwNR9TQik/edit#gid=1697053"
          moz-do-not-send="true">https://docs.google.com/spreadsheets/d/1zURL1UlDST8lnvw3dMlNWN6pkLX6EVF6TDBwNR9TQik/edit#gid=1697053</a></div>
      <div class="moz-cite-prefix"><br>
      </div>
      <div class="moz-cite-prefix">On 2019-09-06 9:38 a.m., Scott Little
        wrote:<br>
      </div>
      <blockquote type="cite"
        cite="mid:601fb79e-9d67-7c59-87c6-190ffa1e9735@windriver.com">
        <div class="moz-cite-prefix">The docker image build was also
          successful.</div>
        <div class="moz-cite-prefix"><br>
        </div>
        <div class="moz-cite-prefix">Scott</div>
        <div class="moz-cite-prefix"><br>
        </div>
        <div class="moz-cite-prefix">On 2019-09-06 12:19 a.m., Little,
          Scott wrote:<br>
        </div>
        <blockquote type="cite"
cite="mid:98F2C8C83A16254EB3DAEC57F3437778BEFB2421@ALA-MBD.corp.ad.wrs.com">
          <style type="text/css" id="owaParaStyle">P {margin-top:0;margin-bottom:0;}</style>
          <div style="direction: ltr;font-family: Tahoma;color:
            #000000;font-size: 10pt;">
            <div>We have a successful ISO build on CENGN.  I will be
              launching a second build to test docker image creation.<br>
            </div>
            <div><br>
            </div>
            <div>I still recommend we stay frozen for one more day while
              we await a sanity result.  You can however start looking
              at the new code structure.<br>
            </div>
            <div><br>
            </div>
            <div>A warning however.  The paths to our most active repos
              has changed.  The 'stx-' prefix has been dropped from must
              repos.  e.g. cgcs-root/stx/stx-integ is now just
              cgcs-root/stx/integ.  What this meens is that a 'repo sync
              --force-sync' will delete cgcs-root/stx/stx-integ and
              create cgcs-root/stx/integ from scratch.  It won't just
              move the repo to the new install path. Deleting the old
              path mean any work you may have saved in a side branch or
              in stash will be gone!</div>
            <div><br>
            </div>
            <div>I strongly recommend you do one of two things.  <br>
            </div>
            <div><br>
            </div>
            <div>1) Back up your work somewhere outside of the directory
              structure controlled by the repo tool before you 'repo
              sync ...'<br>
            </div>
            <div><br>
            </div>
            <div>2) Set up a new root directory and start fresh with
              'repo init ...' and 'repo sync ...'<br>
            </div>
            <div><br>
            </div>
            <div style="font-family: Times New Roman; color: #000000;
              font-size: 16px">
              <hr tabindex="-1">
              <div id="divRpF150681" style="direction: ltr;"><font
                  size="2" face="Tahoma" color="#000000"><b>From:</b>
                  Scott Little [<a class="moz-txt-link-abbreviated"
                    href="mailto:scott.little@windriver.com"
                    moz-do-not-send="true">scott.little@windriver.com</a>]<br>
                  <b>Sent:</b> September 4, 2019 9:50 AM<br>
                  <b>To:</b> <a class="moz-txt-link-abbreviated"
                    href="mailto:starlingx-discuss@lists.starlingx.io"
                    moz-do-not-send="true">starlingx-discuss@lists.starlingx.io</a><br>
                  <b>Subject:</b> Re: [Starlingx-discuss] [Important]
                  repo restructuring<br>
                </font><br>
              </div>
              <div>
                <div class="moz-cite-prefix">Reminder</div>
                <div class="moz-cite-prefix"><br>
                </div>
                <div class="moz-cite-prefix">Please treat the code base
                  as frozen.  No gerrit reviews, other than the
                  restructuring reviews I'll be publishing today, should
                  be receiving a WF+1 until further notice.</div>
                <div class="moz-cite-prefix"><br>
                </div>
                <div class="moz-cite-prefix">Thanks for your
                  cooperation.</div>
                <div class="moz-cite-prefix"><br>
                </div>
                <div class="moz-cite-prefix">Scott</div>
                <div class="moz-cite-prefix"><br>
                </div>
                <div class="moz-cite-prefix"><br>
                </div>
                <div class="moz-cite-prefix">On 2019-09-03 2:33 p.m.,
                  Scott Little wrote:<br>
                </div>
                <blockquote type="cite">
                  <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">
                    <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/"
                        target="_blank" rel="noopener noreferrer"
                        moz-do-not-send="true">
                        https://review.opendev.org/#/c/672288/</a></p>
                    <p>[2] <a
                        href="https://storyboard.openstack.org/#!/story/2006166"
                        target="_blank" rel="noopener noreferrer"
                        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"
                      target="_blank" rel="noopener noreferrer"
                      moz-do-not-send="true">
https://docs.google.com/spreadsheets/d/1zURL1UlDST8lnvw3dMlNWN6pkLX6EVF6TDBwNR9TQik/edit#gid=1697053891</a>
                    <br>
                    <fieldset class="mimeAttachmentHeader"
                      target="_blank" rel="noopener noreferrer"> </fieldset>
                    <pre class="moz-quote-pre">_______________________________________________
Starlingx-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Starlingx-discuss@lists.starlingx.io" target="_blank" rel="noopener noreferrer" moz-do-not-send="true">Starlingx-discuss@lists.starlingx.io</a>
<a class="moz-txt-link-freetext" href="http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss" target="_blank" rel="noopener noreferrer" moz-do-not-send="true">http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss</a>
</pre>
                  </blockquote>
                  <p><br>
                  </p>
                  <br>
                  <fieldset class="mimeAttachmentHeader" target="_blank"
                    rel="noopener noreferrer"> </fieldset>
                  <pre class="moz-quote-pre">_______________________________________________
Starlingx-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Starlingx-discuss@lists.starlingx.io" target="_blank" rel="noopener noreferrer" moz-do-not-send="true">Starlingx-discuss@lists.starlingx.io</a>
<a class="moz-txt-link-freetext" href="http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss" target="_blank" rel="noopener noreferrer" moz-do-not-send="true">http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss</a>
</pre>
                </blockquote>
                <p><br>
                </p>
              </div>
            </div>
          </div>
          <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" moz-do-not-send="true">Starlingx-discuss@lists.starlingx.io</a>
<a class="moz-txt-link-freetext" href="http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss" moz-do-not-send="true">http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss</a>
</pre>
        </blockquote>
        <p><br>
        </p>
        <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" moz-do-not-send="true">Starlingx-discuss@lists.starlingx.io</a>
<a class="moz-txt-link-freetext" href="http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss" moz-do-not-send="true">http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss</a>
</pre>
      </blockquote>
      <p><br>
      </p>
      <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>