<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=gb2312">
<style type="text/css" id="owaParaStyle"></style>
</head>
<body fpstyle="1" ocsi="0">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 12pt;">
<div>Hello, as the Trio2o repository has been established, it's time for us to discuss the freeze date and tagging(newton branch) for the last release of Tricircle with gateway function.</div>
<div><br>
</div>
<div>The freeze date is the gate for patches to be merged before tagging(newton branch). If a patch can't finish review process before the freeze date, and not able to be merged in Tricircle, then it's suggested to be handled like this:</div>
<div><br>
</div>
<div>1. If it's networking automation related patch, continue the review process in Tricircle after tagging(newton branch), will be merged in Tricircle trunk in the future <span style="font-size: 12pt;">.</span></div>
<div><br>
</div>
<div>2. <span style="font-size: 12pt;">If it's gateway related patch, abandon the patch, re-submit the patch in Trio2o.</span></div>
<div><span style="font-size: 12pt;"><br>
</span></div>
<div>3. If it's patch about pod management, for it's common feature, so continue the <span style="font-size: 12pt;">review process in tricircle after </span>tagging(newton branch) <span style="font-size: 12pt;">, and submit a new patch for this feature in
Trio2o separately.</span></div>
<div><span style="font-size: 12pt;"><br>
</span></div>
<div>Exception request after freeze date, before tagging<span style="font-size: 12pt;">(newton branch)</span><span style="font-size: 12pt;">: If there is some patch must be merged before the tagging</span><span style="font-size: 12pt;">(newton branch)</span><span style="font-size: 12pt;">,
then need to send the exception request in the mail-list for the patch, and approved by PTL.</span></div>
<div><br>
</div>
<div>That means we need to define a deadline for patches to be merged in Tricircle before tagging(newton branch), and define the scope of patches wish to be merged in Trcircle before splitting. </div>
<div><br>
</div>
<div>Your thoughts, proposal for the freeze date and patches to be merged?</div>
<div><br>
</div>
<div>(As the old thread containing both Trio2o and Tricircle in the subject, not good to follow, so a new thread is started)</div>
<div><br>
</div>
<div>Best Regards</div>
<div>Chaoyi Huang (joehuang)</div>
<div><br>
</div>
<div>
<hr tabindex="-1" style="font-family: "Times New Roman";">
<div id="divRpF721335" style="font-family: "Times New Roman"; direction: ltr;"><font face="Tahoma" size="2" color="#000000"><b>From:</b> joehuang<br>
<b>Sent:</b> 18 September 2016 16:34<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> RE: [openstack-dev] [tricircle][trio2o] trio2o git repo ready and tricircle splitting<br>
</font><br>
</div>
<div style="font-family: "Times New Roman";"></div>
<div style="font-family: "Times New Roman";">
<div style="direction: ltr; font-family: Tahoma; font-size: 10pt;">Thank you for your comment, Zhiyuan.
<div><br>
</div>
<div>For pod management, because these two projects need to run independently, I think submit patches separately as needed may be a better choice. </div>
<div><br>
</div>
<div>Best Regards</div>
<div>Chaoyi Huang(joehuang)<br>
<div style="font-family: "Times New Roman"; font-size: 16px;">
<hr tabindex="-1">
<div id="divRpF853651" style="direction: ltr;"><font face="Tahoma" size="2" color="#000000"><b>From:</b> Vega Cai [luckyvega.g@gmail.com]<br>
<b>Sent:</b> 18 September 2016 16:27<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [tricircle][trio2o] trio2o git repo ready and tricircle splitting<br>
</font><br>
</div>
<div></div>
<div>
<div dir="ltr">+1 for the proposal. What about the codes for Pod operation? It seems that both Tricircle and Trio2o need these codes. We submit patches to these two projects separately?
<div><br>
</div>
<div>Zhiyuan</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">joehuang <<a href="mailto:joehuang@huawei.com" target="_blank">joehuang@huawei.com</a>>于2016年9月18日周日 下午4:17写道：<br>
</div>
<blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div>
<div style="direction: ltr; font-family: Tahoma; font-size: 10pt;">hello, team,
<div><br>
</div>
<div>Trio2o git repository is ready now: <span style="font-size: 13.3333px;"><a href="https://github.com/openstack/trio2o" target="_blank">https://github.com/openstack/trio2o</a></span></div>
<div><br>
</div>
<div>The repository inherited all files and commit messages from Tricircle.</div>
<div><br>
</div>
<div>It's now the time start to do the tricircle splitting: a blue print is registere for <span style="font-size: 13.3333px;">Tricircle</span><span style="font-size: 13.3333px;"> </span><span style="font-size: 10pt;">cleaning: </span><a href="https://blueprints.launchpad.net/tricircle/+spec/make-tricircle-dedicated-for-networking-automation-across-neutron" target="_blank">https://blueprints.launchpad.net/tricircle/+spec/make-tricircle-dedicated-for-networking-automation-across-neutron</a>.<span style="font-size: 10pt;">There
are lots of documentation work to do. Please review these doc in the BP, thanks.</span></div>
<div><br>
</div>
<div>There are some proposal for patches during the splitting:</div>
<div><br>
</div>
<div>1. For patch which is already in review status, let's review it in Tricircle (no matter it's for Trio2o or Tricircle), after it's get merged, then port it to Trio2o. After all patches get merged, let's have a last tag for Tricircle to cover both gateway
and networking automation function. Then the cleaning will be done in Tricircle to make Tricircle as a project for networking automation only </div>
<div>2. For new patch which is only applicable to Trio2o, I propose that we submit such patches in Trio2o only, no need to submit in Tricircle.</div>
<div><br>
</div>
<div>Would like to know your thoughts on the splitting.</div>
<div><br>
</div>
<div>Best Regards</div>
<div>Chaoyi Huang(joehuang)</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div> </div>
</div>
</div>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank" title="Ctrl+Click to follow link">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" title="Ctrl+Click to follow link">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></blockquote>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div></div>
</div>
</body>
</html>