[openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

Flavio Percoco flavio at redhat.com
Mon Jan 25 15:06:36 UTC 2016

On 20/01/16 13:23 -0430, Flavio Percoco wrote:
>Thoughts? Feedback?

Hey Folks,

Thanks a lot for the feedback. Great comments and proposals in the many replies.
I've gone through the whole thread and collected the most common feedback.
Here's the summary:

- The general idea of planning some sort of stabilization for a project is good
  but considering a cycle for it is terrible. It'd be easier if development
  cycles would be shorter but the 6-month based development cycles don't allow
  for planning this properly.

- Therefore, milestones are more likely to be good for this but there has to be
  a good plan. What will happen with on-going features? How does a project
  decide what to merge or not? Is it really going to help with reviews/bugs
  backlog? or would this just increase the bakclog?
- We shouldn't need any governance resolution/reference for this. Perhaps a
  chapter/section on the project team guide should do it.

- As other changes in the commuity, it'd be awesome to get feedback from a
  project doing this before we start encouraging other projects to do the same.

I'll work on adding something to the project team guide that covers the above

did I miss something? Anything else that we should add and or consider?


Flavio Percoco
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160125/006b636d/attachment.pgp>

More information about the OpenStack-dev mailing list