Open Stack

On 16 March 2016 at 19:58, Armando M. <armamig at gmail.com> wrote:

> An update:
>
> On 15 March 2016 at 21:38, Armando M. <armamig at gmail.com> wrote:
>
>> Neutrinos,
>>
>> I believe we reached the point [1] where RC1 can be cut [2]. If I made an
>> error of judgement, or any other catastrophic failure arises, please report
>> a bug, and tag it as mitaka-rc-potential [3]. Please, sign off on
>> postmortem [4], so that we can finalize the specs status for Mitaka and
>> open up to Newton.
>>
>> Please, consider this the last warning to ensure that everything is in
>> the right order so that you can feel proud of what you and your teammates
>> have accomplished this release!
>>
>
> We bumped [2] already thanks to Cedric finding DB migration issues with
> Postgres. I am about to bump [2] again to contain Kevin's fix for bug
> 1513765. Anything that landed in between is rather safe. At this point I
> don't expect to see any other rc-potential fix that's gonna be in shape in
> time for the end of the week. Salvatore mentioned something odd about
> quota, but until we find out more, and judge whether we need an RC2, it's
> time we draw a line and pull the trigger on RC1, once change for bug
> 1513765 lands.
>

RC1 was released about the same time change [1] landed. As a result, some
upstream gate jobs are now failing both in master and stable/mitaka. This
doesn't mean that RC1 is useless, so don't panic!

Please bear with us until we rectify the situation, but if you wondered if
we needed an RC2 now, clear your doubts, because we obviously will.

A.

[1] https://review.openstack.org/#/c/292573


>
>
>>
>> Cheers,
>> Armando
>>
>> [1] https://launchpad.net/neutron/+milestone/mitaka-rc1
>> [2] https://review.openstack.org/#/c/292445/
>> [3]
>> https://bugs.launchpad.net/neutron/+bugs?field.tag=mitaka-rc-potential
>> [4] https://review.openstack.org/#/c/286413/
>> [5] https://review.openstack.org/#/c/283383/
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160317/8d576939/attachment.html>