Re: [openstack-dev] [Fuel] 6.0 blueprints cleanup

2014-08-11 Thread Mike Scherbakov
+2, yes please On Mon, Aug 11, 2014 at 7:42 PM, Dmitry Borodaenko wrote: > All, > > Please refer to this email for a list of information that has to be > populated in a blueprint before it can be assigned and scheduled: > http://lists.openstack.org/pipermail/openstack-dev/2014-August/042042.htm

Re: [openstack-dev] [Fuel] 6.0 blueprints cleanup

2014-08-11 Thread Dmitry Borodaenko
All, Please refer to this email for a list of information that has to be populated in a blueprint before it can be assigned and scheduled: http://lists.openstack.org/pipermail/openstack-dev/2014-August/042042.html Please don't schedule a blueprint to 6.0 until it has these details and its assigne

[openstack-dev] [Fuel] 6.0 blueprints cleanup

2014-08-11 Thread Dmitry Pyzhov
We've moved all blueprints from 6.0 to 'next' milestone. It has been done in order to better view of stuff that we really want to implement in 6.0. Feature freeze for 6.0 release is planned to 18th of September. If you are going to merge your blueprint before that date, you can move it to 6.0 mile