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 assignees are confirmed. On Mon, Aug 11, 2014 at 8:30 AM, Dmitry Pyzhov <dpyzhov at mirantis.com> wrote: > 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 > milestone and 6.0.x series. But blueprint must have fixed scope and must be > assigned to person who will lead this activity. > > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Dmitry Borodaenko