Checkout Tools
  • last updated 1 hour ago
Constraints: committers
Constraints: files
Constraints: dates
In 'staging': catch-up merge from 'publish'
  1. … 4 more files in changeset.
* site/staging/download.html: Announce 1.14 as the latest LTS, not "regular".

* site/staging/download.html: We only have LTS releases now so comment out

the "regular releases" subsection on this page.

* site/staging/download.html: 1.14 is an LTS, move download links to the

corresponding section.

* site/staging/download.html: Re-apply changes from r1878166 to the staging

site, with hopefully fixed HTML.

In 'staging': catch-up merge from 'publish'
In 'staging': catch-up merge from 'publish'
* docs/release-notes/1.14.html

(#python-is-optional): Make it possible to link to the "Python is Optional" box.

In 'staging': 1.14 release notes: Explain when/how Python is required

* docs/release-notes/1.14.html:

("Python is Optional" note box):

Explain in detail when Subversion requires Python, and also when

it does not, replacing short and vague paragraph.

Suggested by: danielsh

In 'staging': catch-up merge from 'publish'.
* staging/docs/release-notes/1.14.html

(python2, python3): Tweak text; link to Py2 EOL PEP.

In 'staging': 1.14 release notes: invite community participation

* docs/release-notes/1.14.html:

("Support for Python 3.x") and

("Support for Python 2.7 is being phased out."):

After describing which versions of Python we intend to support,

add text to the effect that we welcome contributions to extend

support to other versions. Also link to:

("Enthusiastic Contributors Welcome!"): New section at end of

release notes, inviting community participation in Subversion's


Suggested by: julianfoad

In 'staging': add tentative Python support info to 1.14 release notes

* docs/release-notes/1.14.html:

(What's New in Apache Subversion 1.14): Add links to new subsections

described below.

("API changes, improvements and language bindings"): New section

with subsections:

- "Support for Python 3.x"

- "Support for Python 2.7 is being phased out."

Written with many helpful thoughts and suggestions:

Suggested by: julianfoad


Sync-merge 'publish' to 'staging'
In 'staging': update downloads page to add KEYS file, following r1869135.
In 'staging': update release notes index; tweak release notes wording.
* staging/download.html: Change recommended version to 1.13.0.
* staging/download.html: Remove pre-release 1.13.0-rc1.
* staging/doap.rdf: Fix date typo.

Found by: hartmannathan

On 'staging': publish Subversion 1.13.0.
Sync-merge 'publish' to 'staging'.
* staging/docs/community-guide/releasing.part.html

(release-stabilization-how-many-votes): Update to reflect mailing-list

consensus that we need two +1s, not just one, for non-LTS backports.

In 'staging': Catch up merge from 'publish'.
In 'staging': Tweak presentation of voting requirements.
In 'staging': Require only one +1 vote for non-LTS backports.
Catch-up merge from 'publish' to 'staging'.
* docs/community-guide/releasing.part.html

(#release-stabilization-how-many-votes): Simplify.

* docs/community-guide/releasing.part.html

(#release-stabilization): Fix broken link.

* docs/community-guide/releasing.part.html: Use markup.
* docs/community-guide/releasing.part.html

(#release-stabilization): Mention and interactive mode.