[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Wrong backports listing on website

From: Julian Foad <julianfoad_at_apache.org>
Date: Wed, 31 Jul 2019 10:53:17 +0100

Daniel Shahaf wrote:
> https://subversion.apache.org/docs/release-notes/#upcoming-patch-release still
> shows 1.11.x changes rather than 1.12.x.
>
> The "11" is hardcoded in two places:
>
> - In the HTML source of site/publish/docs/release-notes/index.html (for the
> prose).

http://svn.apache.org/r1864040 : Make the 'upcoming changes' script tell
which branch it's reporting, and remove that info from the prose.

-- Except for one remaining place, a link to 'STATUS' file.

> - In the Puppet manifest, [1], for the actual commands to use.

I sent a merge request to change it from 'cd ~/src/svn/1.11.x' to 'cd
~/src/svn/latest' and made a symlink 'latest -> 1.12.x' locally on
svn-qavm3 (and will do the same on the new svn-qavm once I can access it).

-- So now that symlink is what needs to be updated for each minor release.

> The immediate fix would be to patch both of these to say "12" rather
> than "11". Then, we should either add this step to the new-minor-branch
> checklist, or [...]

http://svn.apache.org/r1864042 : Document a step for updating the
'upcoming changes' branch for a new minor release.

That should be enough to fix it, for now.

Thanks for reporting this, Daniel.

- Julian
Received on 2019-07-31 11:53:21 CEST

This is an archived mail posted to the Subversion Dev mailing list.