Details
-
Task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
trunk
-
None
-
None
Description
https://subversion.apache.org/docs/release-notes/#upcoming-patch-release is generated by https://svn.apache.org/repos/asf/subversion/site/tools/upcoming.py. Currently, that script expects to be run from a working copy of ^/subversion/branches/1.A.x and emits the changes for that branch. That gives rise to a requirement to update the symlink ~svnsvn/src/svn/latest whenever we create a new minor release. (That symlink currently points to ./1.12.x. It's used by https://github.com/apache/infrastructure-puppet/blob/deployment/modules/svnqavm_pvm_asf/manifests/init.pp.)
Teach upcoming.py to figure out automatically which branch is latest¹ and automatically show changes for that branch.
The linked Web page documents "You could find the changes queued for another release line by running that script in a working copy of, for example, the 1.10.x branch". Update that sentence, if needed.
(Also, not strictly part of this issue, but if you can figure out a way to auto-update the link to 1.12.x/STATUS in that Web page, that'd be nice to have.)
¹ proof of concept code: https://mail-archives.apache.org/mod_mbox/subversion-dev/201907.mbox/%3c20190731164934.bfu6rocnijgezzhd@tarpaulin.shahaf.local2%3e