[openstack-dev] [murano] idea of introducing a spec-freeze, during M cycle

Kirill Zaitsev kzaitsev at mirantis.com
Sun Jul 12 21:29:14 UTC 2015

We had discussed this (see subj) interesting idea, during our latest meeting in IRC (http://eavesdrop.openstack.org/meetings/murano/2015/murano.2015-07-07-17.01.html)
The idea was borrowed from nova, who froze their specs shortly after L1 release. The reasoning behind this is rather simple, as adding something, that requires a spec during a 2d half of the cycle, seems like a not so good idea. Knowing that there would be a spec freeze of some sort, would probably 
1) make contributors want to write their specs beforehan
2) make reviewers review specs more often (although I’m not really sure if there is a good way to encourage spec reviews)

What do you think about such an idea? 
Obviously introducing a spec-freeze for liberty (without proper prior notice) is a bad thing to do. But sounds like a reasonable idea for M cycle. Somewhere between M-1 and M-2, maybe? What do you think?

Kirill Zaitsev
Murano team
Software Engineer
Mirantis, Inc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150713/85ccef8d/attachment.html>

More information about the OpenStack-dev mailing list