Excerpts from Markus Zoeller's message of 2015-11-19 18:37:34 +0100: > If you ever had a patch which contained "UpgradeImpact" or "DocImpact", > this mail is for you. You may have already heard of "reno" and how it > will change the handling of the release notes. If not, [1] is the > announcement and [2] is an example. I wanted to preemptively ask > if we want to add some guidelines when it is appropriate to add such > a release note and in which cases not. The Keystone folks did already > create a statement [3] and the Cinder folks are planning to do so [4]. > The Keystone list looks reasonable to me. Any thoughts on that? > > [1] 2015-11-03, "new change management tools and processes for stable > /liberty and mitaka": > > http://lists.openstack.org/pipermail/openstack-dev/2015-November/078301.html > [2] https://review.openstack.org/#/c/197912/37 > [3] > http://docs.openstack.org/developer/keystone/developing.html#release-notes > [4] > http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-11-18-16.00.log.html > > Regards, Markus Zoeller (markus_z) > We're also working on a list for the project team guide in https://review.openstack.org/#/c/246455/ I would love to have some review feedback and additional suggestions added there or in follow-up patches. Doug