<div dir="ltr">Alexey,<div><br></div><div>Thank you for the vote. We expect to spend 2 more days on patch [1] and [2], and then another 2 days to finish patch [3]. With reviewers help, [1] and [2] will land by Wednesday, while [3] is due Thursday.</div><div><br></div><div>[1] <a href="https://review.openstack.org/#/c/202969/">https://review.openstack.org/#/c/202969/</a></div><div>[2] <a href="https://review.openstack.org/#/c/203537/">https://review.openstack.org/#/c/203537/</a></div><div>[3] <a href="https://review.openstack.org/#/c/203536/">https://review.openstack.org/#/c/203536/</a></div><div><br></div><div>--</div><div>Best regards,</div><div>Oleg Gelbukh</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jul 24, 2015 at 3:26 PM, Aleksey Kasatkin <span dir="ltr"><<a href="mailto:akasatkin@mirantis.com" target="_blank">akasatkin@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">+1 for an exception. Do we have time estimate though?<span class="HOEnZb"><font color="#888888"><br><br></font></span></div><div class="gmail_extra"><span class="HOEnZb"><font color="#888888"><br clear="all"><div><div><div dir="ltr">Aleksey Kasatkin
<br><br></div></div></div></font></span><div><div class="h5">
<br><div class="gmail_quote">On Fri, Jul 24, 2015 at 2:46 PM, Sebastian Kalinowski <span dir="ltr"><<a href="mailto:skalinowski@mirantis.com" target="_blank">skalinowski@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">+1 for this exception - as Evgeniy said it is developed not in the core but in extension and risk is low.<br></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">2015-07-24 10:17 GMT+02:00 Evgeniy L <span dir="ltr"><<a href="mailto:eli@mirantis.com" target="_blank">eli@mirantis.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>If we have a rule that feature freeze exceptions should have essential priority,</div><div>I'm not sure if it matters how risky it's, the risk is low, but it's not zero.</div><div><br></div><div>Thanks,</div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jul 23, 2015 at 9:09 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"><span style="font-size:small;line-height:20px">Oleg,</span><div style="font-size:small;line-height:20px">considering that your feature is essential for the release, sounds like there is no way we can't give an exception.</div><div style="font-size:small;line-height:20px"><br></div><div style="font-size:small;line-height:20px">I'm glad that it's perceived by low risk by core reviewer from Nailgun team (Evgeny). If there are no concerns from other, then we are giving FF exception. However, I'd like to understand how much it will take to finish this work and additional resources required.</div><div style="font-size:small;line-height:20px"><br></div><div style="font-size:small;line-height:20px">We need to switch to bugfix work, and the more we continue working on features / enhancements, the less confidence I have that we can meet HCF deadline.</div><div style="font-size:small;line-height:20px"><br></div><div style="font-size:small;line-height:20px">Thanks,</div></div><div><div><br><div class="gmail_quote"><div dir="ltr">On Thu, Jul 23, 2015 at 11:00 AM Evgeniy L <<a href="mailto:eli@mirantis.com" target="_blank">eli@mirantis.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>The patch into Nailgun requires additional work to do, but as far as I can see</div><div>it doesn't affect any other parts of the system, also it's implemented as an</div><div>extension, which means if the feature will introduce bugs which we won't</div><div>be able to fix in a required time, it can be easily disabled without removing from</div><div>master with just removing one line from a file [1] (removing it from extensions list).</div><div><br></div><div>So I think it's ok to accept environment upgrade feature as an exception for feature</div><div>freeze.</div><div><br></div><div>Thanks,</div><div><br></div><div>[1] <a href="https://review.openstack.org/#/c/202969/7/nailgun/nailgun/extensions/base.py" target="_blank">https://review.openstack.org/#/c/202969/7/nailgun/nailgun/extensions/base.py</a></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 22, 2015 at 10:18 PM, Oleg Gelbukh <span dir="ltr"><<a href="mailto:ogelbukh@mirantis.com" target="_blank">ogelbukh@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">Team,<div><br></div><div>I would like to request an exception from the Feature Freeze for Environment Upgrade extensions added to the Nailgun API [1]. The Nailgun side of the feature is implemented in the following CRs:</div><div><br></div><div><a href="https://review.openstack.org/#/q/status:open+topic:bp/nailgun-api-env-upgrade-extensions,n,z" target="_blank">https://review.openstack.org/#/q/status:open+topic:bp/nailgun-api-env-upgrade-extensions,n,z</a><br></div><div><br></div><div>These changes are implemented as an extension [2] to the Nailgun. It barely touches the core code and doesn't change the existing functionality.</div><div><br></div><div>Please, respond if you have any questions or concerns related to this request.</div><div><br></div><div>Thanks in advance.</div><div><br></div><div>[1] <a href="https://review.openstack.org/#/c/192551/" target="_blank">https://review.openstack.org/#/c/192551/</a></div><div>[2] <a href="https://review.openstack.org/#/q/topic:bp/volume-manager-refactoring,n,z" target="_blank">https://review.openstack.org/#/q/topic:bp/volume-manager-refactoring,n,z</a></div><div><br></div><div>--</div><div>Best regards,</div><div>Oleg Gelbukh</div></div>
<br>__________________________________________________________________________<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">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">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></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">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">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div></div></div><span><font color="#888888"><div dir="ltr">-- <br></div><div dir="ltr">Mike Scherbakov<br>#mihgen</div>
</font></span><br>__________________________________________________________________________<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">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">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>
</div></div><br>__________________________________________________________________________<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">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">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>
</div></div><br>__________________________________________________________________________<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">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">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div></div>
<br>__________________________________________________________________________<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">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">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>