Julian Foad wrote on Mon, Dec 10, 2018 at 18:29:31 +0000: > It would be good for visibility if we could show on the web site what changes > are waiting to be released in maintenance branches. Both merged and nominated > changes. >
Sure. > How could we implement that to get an acceptable display on our web site? > One option: Start using the CHANGES-info-in-log-message convention more pervasively, and then write a script that: 1. Queries the repository for trunk revnums that have been merged to the stable branch since the last tag; 2. Parses STATUS for trunk revnums that are candidates for merging (this is easy to implement using backport.py's libraries); 3. Synthesizes a CHANGES-like listing of all those revisions, distinguishing the ones that have been merged and the ones that haven't yet been; and say that even the ones that haven't yet been merged probably will be before the next release (this is not a promise, but simply a reflection of our practice of approving most or all pending nominations before a release). > (While we're there, we might as well include a list of the new changes on > trunk too, mightn't we?) I think this, too, boils to writing the CHANGES info ahead of time, otherwise the work would amount to a custom user interface around «svn mergeinfo --show-revs=eligible ^/subversion/trunk ^/subversion/tags/1.latestx.latesty» — which is a job better suited for third parties such as viewvc or whimsy. (For one, implementing the functionality in viewvc or whimsy would make it available to all svn-using ASF projects, not just us.) Cheers, Daniel
