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)
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
