Julian Foad

Clarify LTS versus regular releases.

Suggested by: Thomas Singer <thomas.singer{_AT_}syntevo.com>

* download.html

Add a notice of latest LTS release after notice of latest regular release.

(#recommended-release): Change the title to "Latest regular release".

State the support period.

(#supported-releases): Change the title to "LTS releases".

State the support period.

Say "1.10 LTS" instead of just "1.10", and for 1.9, everywhere.

* index.html, news.html: remove incorrect anchors in links to download page in recent news items. Better with no anchor at all.
* site-nav.html (site-nav-menu): Remove currently unnecessary '?update=...' parameter from download link.
Supported releases: Remove 'support period' column.

The info in it was simply wrong. Rather than correcting it, remove it as

correct and clearer details are already stated on the linked 'release planning' page.

Add recent CVEs to the list, and add my signature on their advisories.
    • ?
    /site/publish/security/CVE-2018-11782-advisory.txt.asc
    • ?
    /site/publish/security/CVE-2019-0203-advisory.txt.asc
Remove a step for updating the 'upcoming changes' branch for a new minor release.

Reverts r1864042, as it is now done a different way:

https://issues.apache.org/jira/browse/SVN-4823 "site: upcoming.py script

should automatically show changes for the latest stable branch".

Disclose CVE-2018-11782 and CVE-2019-0203.
    • ?
    /site/publish/security/CVE-2018-11782-advisory.txt
Document a step for updating the 'upcoming changes' branch for a new minor release.
Make the 'upcoming changes' script tell which branch it's reporting, and remove that info from the prose.
Announce Subversion 1.12.2, 1.10.6, 1.9.12.

A merge from 'staging' plus updating the date of the news item.

Add 'Reply-To: users@' in the 'release.py write-announcement' templates.
Catch-up merge from publish/ to staging/.
* publish/docs/community-guide/releasing.part.html (tarball-signing):

Add sub-headings and format the requirements as a list, for clarity.

Fix 'release.py sign-candidates' for future versions >= 2.0.

* tools/dist/release.py

(sign_candidates): Fix the version number comparison.

Fix release.py check-sigs/write-downloads: 1.9.1 matched also 1.9.10, etc.

* tools/dist/release.py

(get_fileinfo): Tighten the version-match glob expression.

(check_sigs): Use get_fileinfo() instead of its own glob expression.

Fix broken cleanup in svn_load_dirs.pl.

* contrib/client-side/svn_load_dirs/svn_load_dirs.pl.in (DESTROY):

Change cwd to the parent of the directory to remove.

Patch by: Geoffrey Alary <geoffrey.alary{_AT_}gmail.com>

Catch-up merge from publish/ to staging/.
On 'staging' branch: following r1863379, correct links in news.
* publish/download.html: Remove old 1.7-era note about '-deps' package.
On 'staging' branch: following r1863379, correct a version number.
On 'staging' branch: publish the 1.12.2, 1.10.6, 1.9.12 releases.
Catch-up merge from publish/ to staging/.
  1. … 6 more files in changeset.
Post-release housekeeping: bump the 1.9.x branch to 1.9.13.
Tagging release 1.9.12
    • ?
    /tags/1.9.12/subversion/include/svn_version.h
Post-release housekeeping: bump the 1.10.x branch to 1.10.7.
Tagging release 1.10.6
    • ?
    /tags/1.10.6/subversion/include/svn_version.h
Post-release housekeeping: bump the 1.12.x branch to 1.12.3.
Tagging release 1.12.2
    • ?
    /tags/1.12.2/subversion/include/svn_version.h
On the '1.9.x' branch: sync 'CHANGES' from trunk.
On the '1.10.x' branch: sync 'CHANGES' from trunk.