[jira] [Commented] (SVN-4823) site: upcoming.py script should automatically show changes for the latest stable branch

["Daniel Shahaf (äñ§€¥£¢ JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SVN-4823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16899109#comment-16899109 ] 

Daniel Shahaf (äñ§€¥£¢) commented on SVN-4823:
----------------------------------------------

Done in a series of small commits, culminating in r1864264.

I assume the next steps are:
 1. Remove {{cd ~/src/svn/latest}} from the cron job.
 2. {{rm ~/src/svn/latest}}
 3. Remove the "Update {{~/src/svn/latest}}" step from HACKING.


 [~julianfoad], Would this conflict with any infra PRs you have in flight? Also, could you take care of step (2) on the new VM? I don't have access to it.

> site: upcoming.py script should automatically show changes for the latest stable branch
> ---------------------------------------------------------------------------------------
>
>                 Key: SVN-4823
>                 URL: https://issues.apache.org/jira/browse/SVN-4823
>             Project: Subversion
>          Issue Type: Task
>          Components: docs_www
>    Affects Versions: trunk
>            Reporter: Daniel Shahaf (äñ§€¥£¢)
>            Priority: Major
>
> [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|https://mail-archives.apache.org/mod_mbox/subversion-dev/201907.mbox/%3c20190731164934.bfu6rocnijgezzhd@tarpaulin.shahaf.local2%3e)]



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)