subversion-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Shahaf (äñ§€¥£¢) (JIRA) <>
Subject [jira] [Commented] (SVN-4823) site: script should automatically show changes for the latest stable branch
Date Fri, 02 Aug 2019 18:16:00 GMT


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: script should automatically show changes for the latest stable branch
> ---------------------------------------------------------------------------------------
>                 Key: SVN-4823
>                 URL:
>             Project: Subversion
>          Issue Type: Task
>          Components: docs_www
>    Affects Versions: trunk
>            Reporter: Daniel Shahaf (äñ§€¥£¢)
>            Priority: Major
> [] is generated
by [] 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 [].)
> Teach 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: [|]

This message was sent by Atlassian JIRA

View raw message