Open Stack

Alexey,

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.

[1] https://review.openstack.org/#/c/202969/
[2] https://review.openstack.org/#/c/203537/
[3] https://review.openstack.org/#/c/203536/

--
Best regards,
Oleg Gelbukh

On Fri, Jul 24, 2015 at 3:26 PM, Aleksey Kasatkin <akasatkin at mirantis.com>
wrote:

> +1 for an exception. Do we have time estimate though?
>
>
> Aleksey Kasatkin
>
>
> On Fri, Jul 24, 2015 at 2:46 PM, Sebastian Kalinowski <
> skalinowski at mirantis.com> wrote:
>
>> +1 for this exception - as Evgeniy said it is developed not in the core
>> but in extension and risk is low.
>>
>> 2015-07-24 10:17 GMT+02:00 Evgeniy L <eli at mirantis.com>:
>>
>>> Hi,
>>>
>>> If we have a rule that feature freeze exceptions should have essential
>>> priority,
>>> I'm not sure if it matters how risky it's, the risk is low, but it's not
>>> zero.
>>>
>>> Thanks,
>>>
>>> On Thu, Jul 23, 2015 at 9:09 PM, Mike Scherbakov <
>>> mscherbakov at mirantis.com> wrote:
>>>
>>>> Oleg,
>>>> considering that your feature is essential for the release, sounds like
>>>> there is no way we can't give an exception.
>>>>
>>>> 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.
>>>>
>>>> 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.
>>>>
>>>> Thanks,
>>>>
>>>> On Thu, Jul 23, 2015 at 11:00 AM Evgeniy L <eli at mirantis.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> The patch into Nailgun requires additional work to do, but as far as I
>>>>> can see
>>>>> it doesn't affect any other parts of the system, also it's implemented
>>>>> as an
>>>>> extension, which means if the feature will introduce bugs which we
>>>>> won't
>>>>> be able to fix in a required time, it can be easily disabled without
>>>>> removing from
>>>>> master with just removing one line from a file [1] (removing it from
>>>>> extensions list).
>>>>>
>>>>> So I think it's ok to accept environment upgrade feature as an
>>>>> exception for feature
>>>>> freeze.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> [1]
>>>>> https://review.openstack.org/#/c/202969/7/nailgun/nailgun/extensions/base.py
>>>>>
>>>>> On Wed, Jul 22, 2015 at 10:18 PM, Oleg Gelbukh <ogelbukh at mirantis.com>
>>>>> wrote:
>>>>>
>>>>>> Team,
>>>>>>
>>>>>> 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:
>>>>>>
>>>>>>
>>>>>> https://review.openstack.org/#/q/status:open+topic:bp/nailgun-api-env-upgrade-extensions,n,z
>>>>>>
>>>>>> These changes are implemented as an extension [2] to the Nailgun. It
>>>>>> barely touches the core code and doesn't change the existing functionality.
>>>>>>
>>>>>> Please, respond if you have any questions or concerns related to this
>>>>>> request.
>>>>>>
>>>>>> Thanks in advance.
>>>>>>
>>>>>> [1] https://review.openstack.org/#/c/192551/
>>>>>> [2]
>>>>>> https://review.openstack.org/#/q/topic:bp/volume-manager-refactoring,n,z
>>>>>>
>>>>>> --
>>>>>> Best regards,
>>>>>> Oleg Gelbukh
>>>>>>
>>>>>>
>>>>>> __________________________________________________________________________
>>>>>> OpenStack Development Mailing List (not for usage questions)
>>>>>> Unsubscribe:
>>>>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>>>
>>>>>>
>>>>>
>>>>> __________________________________________________________________________
>>>>> OpenStack Development Mailing List (not for usage questions)
>>>>> Unsubscribe:
>>>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>>
>>>> --
>>>> Mike Scherbakov
>>>> #mihgen
>>>>
>>>>
>>>> __________________________________________________________________________
>>>> OpenStack Development Mailing List (not for usage questions)
>>>> Unsubscribe:
>>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>
>>>>
>>>
>>>
>>> __________________________________________________________________________
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150724/f363c298/attachment.html>