Hi,

Lets keep track of things for Nova here:
https://etherpad.openstack.org/p/nova-icehouse-blueprint-cull

In a few hours I will start reviewing all the blueprints that are not
"Needs Code Review" and pushing them into "next". Anything with some
"live" code will probably go into Juno-1, if that makes sense.

Then I will look at "Needs Code Review" blueprints to check they are
just blocked waiting for a review.

Do shout up if you feel like we miss-understood the current status of
your blueprint. If you think your blueprint has the wrong status,
please update that very soon, ideally yesterday.

Hopefully I can then publish a list of reviews we should concentrate
on, in the hope of getting as many of those blueprints with code
reviewed, as quickly as possible. (My script is almost ready for
that).

Thanks in advance for not hating me :)

johnthetubaguy


On 17 February 2014 10:07, Thierry Carrez <thie...@openstack.org> wrote:
> Hi everyone,
>
> Just a quick reminder that some of our projects have a deadline tomorrow
> (end of day, Feb 18th) for proposing Icehouse feature code for review.
> To my knowledge, this affects Nova, Neutron, Keystone and Cinder.
>
> This means that starting on Wednesday, Feb 19, blueprints for those
> projects that are not at "Needs Code review" status might get deferred
> to the Juno cycle. This shall allow better prediction of the features
> that are likely to make it for Icehouse, as well as a better review
> focus for the two weeks that separate us from Icehouse Feature Freeze
> (March 4).
>
> See https://wiki.openstack.org/wiki/FeatureProposalFreeze for more
> information.
>
> --
> Thierry Carrez (ttx)
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to