On Mon, Feb 23, 2015, Joe Gordon <[email protected]> wrote: > What this actually means: > > - Stop approving blueprints for specific stable releases, instead just > approve them and target them to milestones. > - Milestones stop becoming Kilo-1, Kilo-2, Kilo-3 etc. and just > become 1,2,3,4,5,6,7,8,9 etc. > - If something misses what was previously known as Kilo-3 it has to > wait a week for what for milestone 4. > - Development focuses on milestones only. So 6 week cycle with say 1 > week of stabilization, finish things up before each milestone
What is the motiviation for having milestones at all? At least in the Nova world, it seems like milestones mean nothing at all. It's just something John Garbutt spends a lot of his time updating that doesn't appear to provide any value to anyone. JE __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
