Re: Display outstanding backported fixes for each release?
From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Tue, 11 Dec 2018 08:29:22 +0000
Julian Foad wrote on Mon, Dec 10, 2018 at 18:29:31 +0000:
> How could we implement that to get an acceptable display on our web site?
Start using the CHANGES-info-in-log-message convention more pervasively,
1. Queries the repository for trunk revnums that have been merged to the
2. Parses STATUS for trunk revnums that are candidates for merging (this
3. Synthesizes a CHANGES-like listing of all those revisions, distinguishing
> (While we're there, we might as well include a list of the new changes on
I think this, too, boils to writing the CHANGES info ahead of time,
This is an archived mail posted to the Subversion Dev mailing list.