Open Stack

On 11 March 2015 at 12:51, Gary Kotton <gkotton at vmware.com> wrote:
> Hi,
> Not 100% sure that I understand. This is for the BP¹s and specs that were
> approved for Kilo.

Basically, yes. No change from previous releases here AFAIK.

It shouldn't affect bug fixes, unless they violate one of the freezes
(like string freeze).

The definitions of each freeze are linked from the release status page:
https://wiki.openstack.org/wiki/Kilo_Release_Schedule

> Bug fixes if I understand are going to be reviewed
> until the release of Kilo.

Basically, yes.

> Is launchpad not a sufficient source for highlighting bugs?

Not sure I understand the question.

The idea of the launchpad bug tag of kilo-rc-potential is to stop
things that stop us releasing kilo. Things targetted for kilo-3 are
basically saying don't ship kilo-3 without fixing this. Everything is
just like previous releases.

We have the trivial patch list, that lives here, but thats purely an
addition to our primary tracking:
https://etherpad.openstack.org/p/kilo-nova-priorities-tracking

Thanks,
John


> On 3/11/15, 2:13 PM, "John Garbutt" <john at johngarbutt.com> wrote:
>
>>Hi,
>>
>>Just a quick update on where we are at with the release:
>>https://wiki.openstack.org/wiki/Kilo_Release_Schedule
>>
>>Please help review all the code we want to merge before FeatureFreeze:
>>https://etherpad.openstack.org/p/kilo-nova-priorities-tracking
>>https://launchpad.net/nova/+milestone/kilo-3
>>
>>Please note, 19th March is:
>>kilo-3 release, General FeatureFreeze, StringFreeze, DepFreeze
>>(that includes all high priority items)
>>
>>Generally patches that don't look likely to merge by 19th March are
>>likely to get deferred around 17th March, to make sure we get kilo-3
>>out the door.
>>
>>As ever, there may be exceptions, if we really need them, but they
>>will have to be reviewed by ttx for their impact on the overall
>>integrated release of kilo. More details will be shared nearer the
>>time.
>>
>>A big ask at this time, is to highlight any release critical bugs that
>>we need to fixe before we can release kilo (and that involves testing
>>things). We are likely to use the kilo-rc-potential tag to track those
>>bugs, more details on that soon.
>>
>>Any questions, please do ask (here or on IRC).
>>
>>Thanks,
>>johnthetubaguy
>>
>>PS
>>Just a reminder you are now free to submit specs for liberty. Specs
>>where there is no clear agreement will be the best candidates for a
>>discussion slot at the summit. Again more on that later.
>>
>>__________________________________________________________________________
>>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