<html><body>
<p><font size="2" face="sans-serif">I like the idea. When writing release notes, the more information we have the better. I usually look at the blueprints that were completed or our specs, but having an additional source (a commit message I could query) is always good.</font><br>
<font size="2" face="sans-serif"><br>
Thanks,<br>
<br>
Steve Martinelli<br>
OpenStack Keystone Core</font><br>
<br>
<img width="16" height="16" src="cid:1__=0ABBF4E8DFC816DE8f9e8a93df938@ca.ibm.com" border="0" alt="Inactive hide details for Matt Riedemann ---2015/07/07 12:13:41 PM---While reviewing a change in nova [1] I mentioned that we s"><font size="2" color="#424282" face="sans-serif">Matt Riedemann ---2015/07/07 12:13:41 PM---While reviewing a change in nova [1] I mentioned that we should have something in the release notes</font><br>
<br>
<font size="1" color="#5F5F5F" face="sans-serif">From: </font><font size="1" face="sans-serif">Matt Riedemann <mriedem@linux.vnet.ibm.com></font><br>
<font size="1" color="#5F5F5F" face="sans-serif">To: </font><font size="1" face="sans-serif">"OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org></font><br>
<font size="1" color="#5F5F5F" face="sans-serif">Date: </font><font size="1" face="sans-serif">2015/07/07 12:13 PM</font><br>
<font size="1" color="#5F5F5F" face="sans-serif">Subject: </font><font size="1" face="sans-serif">[openstack-dev] Thoughts on ReleaseNoteImpact git commit message tag</font><br>
<hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br>
<br>
<br>
<tt><font size="2">While reviewing a change in nova [1] I mentioned that we should have <br>
something in the release notes for Liberty on the change. Typically for <br>
this I ask that the UpgradeImpact tag is added to the commit message <br>
because at the end of a release I search git/gerrit for any commits that <br>
have UpgradeImpact in them since the last major release (Kilo in this <br>
case) and then we should see if those need mentioning in the release <br>
notes upgrade impacts section for Nova (which they usually do).<br>
<br>
The thing is, UpgradeImpact isn't always appropriate for the change, but <br>
DocImpact is used too broadly and as far as I can tell, it's not really <br>
for updating release notes [2]. It's for updating stuff found in <br>
docs.openstack.org.<br>
<br>
So we kicked around the idea of a ReleaseNoteImpact tag so that we can <br>
search for those at the end of the release in addition to UpgradeImpact.<br>
<br>
Are any other projects already doing something like this? Or do we just <br>
stick with UpgradeImpact? Per the docs [3] it mentions release notes <br>
but for configuration changes - which not everything in the release <br>
notes for an upgrade impact requires a config change, some are <br>
behavior/usage changes. In this specific case in [1], it's actually <br>
probably an APIImpact, albeit indirectly.<br>
<br>
Anyway, just putting this out there to see how other projects are <br>
handling tagging changes for inclusion in the release notes.<br>
<br>
[1] </font></tt><tt><font size="2"><a href="https://review.openstack.org/#/c/189632/">https://review.openstack.org/#/c/189632/</a></font></tt><tt><font size="2"><br>
[2] </font></tt><tt><font size="2"><a href="https://wiki.openstack.org/wiki/Documentation/DocImpact">https://wiki.openstack.org/wiki/Documentation/DocImpact</a></font></tt><tt><font size="2"><br>
[3] </font></tt><tt><font size="2"><a href="http://docs.openstack.org/infra/manual/developers.html#peer-review">http://docs.openstack.org/infra/manual/developers.html#peer-review</a></font></tt><tt><font size="2"><br>
<br>
-- <br>
<br>
Thanks,<br>
<br>
Matt Riedemann<br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>
</font></tt><tt><font size="2"><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></font></tt><tt><font size="2"><br>
<br>
</font></tt><br>
<br>
</body></html>