<div dir="ltr">The right way, I believe, should be the following:<div><ol><li>Change the current development focus to 7.0 in LP</li><li>Ensure that every single commit which was merged into master after branches created targets correct milestones (it can be only 7.0 or both 7.0 and 6.1)</li><li>Ensure that remaining 6.1 targeted bugs which have to be landed in 6.1, target both 6.1 & 7.0 now</li></ol><div>Then, if someone merges fix to master - only 7.0 target will be closed as Fix Committed. 6.1 will keep open unless we backport the patch to stable/6.1.</div></div><div><br></div><div>DevOps team, can you help in executing this?</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 8, 2015 at 2:42 PM, Mike Scherbakov <span dir="ltr"><<a href="mailto:mscherbakov@mirantis.com" target="_blank">mscherbakov@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Eugene, thanks for communication.<div><br></div><div>Fuel DevOps team, when should we expect changes to builds page [1]? Namely, I'd like to ensure 6.1 builds are switched to stable/6.1 branch, and new Jenkins jobs created to make builds from master (7.0).</div><div><br></div><div>Everyone - we have to be extremely careful now and ensure that no patch is missed from stable/6.1 branch, which was intended to be fixed in 6.1. QA team, count on you to pay special attention to Fix Committed bugs which became closed after branches were created.</div><div><br></div><div>Thanks!</div><div><br></div><div>[1] <a href="https://ci.fuel-infra.org/" target="_blank">https://ci.fuel-infra.org/</a></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Mon, Jun 8, 2015 at 10:50 AM, Eugene Bogdanov <span dir="ltr"><<a href="mailto:ebogdanov@mirantis.com" target="_blank">ebogdanov@mirantis.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
<div style="color:rgb(0,0,0);background-color:rgb(255,255,255)" bgcolor="#FFFFFF" text="#000000">
Hello everyone,<br>
<br>
Please be informed that Hard Code Freeze for MOS <span style="display:inline;font-size:inherit;padding:0pt"><span style="display:inline;font-size:inherit;padding:0pt"><span style="display:inline;font-size:inherit;padding:0pt"><span style="display:inline;font-size:inherit;padding:0pt">6.1</span></span></span></span>
Release is
officially in action. As mentioned earlier, stable/6.1 branch was
created for the following repos:<br>
<br>
fuel-astute<br>
fuel-docs<br>
fuel-library<br>
fuel-main<br>
fuel-ostf<br>
fuel-qa<br>
fuel-web<br>
<br>
Bug reporters, please do not forget to target both master and 6.1
(stable/6.1) milestones since now. Also, please remember that all fixes
for stable/6.1 branch should first be applied to master and then
cherry-picked to stable/6.1. As always, please
ensure that you do NOT merge changes to stable branch first. It always
has to
be a backport with the same Change-ID. Please see more on this at [1]<span><font color="#888888"><br>
<br>
-- <br>
<div>EugeneB<br>
<br>
[1]
<a href="https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Backport_bugfixes_to_stable_release_series" target="_blank">https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Backport_bugfixes_to_stable_release_series</a><br>
</div>
</font></span></div>
<br></div></div>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><span class="HOEnZb"><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div><div dir="ltr">Mike Scherbakov<br>#mihgen<br><br></div></div>
</font></span></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr">Mike Scherbakov<br>#mihgen<br><br></div></div>
</div>