Last modified: 2011-01-25 00:31:30 UTC
I would find it handy to be able to automatically or semi-automatically build a list of new changes in the software when we run updates. The easiest way would be to diff the RELEASE-NOTES file and just spit out all the new entries -- but people frequently forget to update it, and important things don't get listed. A tool to slurp together lines from accepted revisions in core code and whitelisted extensions and build a first-draft "what's new" list would be pretty helpful. Alternately, a nice bug "needs release notes" button to plug on any rev. ;)
An issue here is that some revisions, however important, don't get RELEASE-NOTES. This applies to stuff like internal rewrites without user-observed changes and fixes for new features that were already in RELEASE-NOTES.
Some of those "rewrites without user-observed changes" actually do have user-observed changes because they introduce bugs. :) It gets a lot easier to track them down if it's clear what's been changed.
(In reply to comment #2) > Some of those "rewrites without user-observed changes" actually do have > user-observed changes because they introduce bugs. :) It gets a lot easier to > track them down if it's clear what's been changed. > True. They are relevant to show in CR of course, all I'm saying is they don't belong in RELEASE-NOTES.
Done in r47271
