release-notes

Checkout Tools
  • last updated 8 hours ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
In 'staging': catch-up merge from 'publish'
  1. … 2 more files in changeset.
In 'staging': catch-up merge from 'publish'
  1. … 4 more files in changeset.
* 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'.
  1. … 1 more file in changeset.
* 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

development.

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

danielsh

Sync-merge 'publish' to 'staging'
  1. … 5 more files in changeset.
In 'staging': update release notes index; tweak release notes wording.
On 'staging': publish Subversion 1.13.0.
  1. … 4 more files in changeset.
Sync-merge 'publish' to 'staging'.
  1. … 9 more files in changeset.
In 'staging': Catch up merge from 'publish'.
  1. … 11 more files in changeset.
Sync-merge from publish
  1. … 17 more files in changeset.
On 'staging' branch: publish the 1.12.2, 1.10.6, 1.9.12 releases.
  1. … 4 more files in changeset.
Catch-up merge from publish/ to staging/.
  1. … 18 more files in changeset.
* staging/docs/release-notes/1.12.html

(github-issue): remove; no longer relevant

* staging/docs/release-notes/1.12.html

(issues): Mention the APR 1.7.0 build problem.

* staging/docs/release-notes/1.12.html

(conflict-resolver): Document improved support for unversioned items.

* staging/docs/release-notes/1.12.html: Document more client- and server-side

changes, based on items in the CHANGES file.

* staging/docs/release-notes/1.12.html

(conflict-resolver): Document resolver features added for 1.12.

* staging/docs/release-notes/index.html (upcoming-patch-release): Explain what it is.
* docs/release-notes/index.html: Remove a completed todo.

The script now supports running on 1.10.x (though the cron job runs 1.11.x

only, as of this writing).

* docs/release-notes/index.html: Change iframe (which rendered small) to SSI.
* docs/release-notes/index.html: Add another todo.
[in staging]

* docs/release-notes/index.html

(#upcoming-patch-release): Add the merges since 1.11.0 (currently, a rough sketch).

Sync-merge publish into staging
  1. … 7 more files in changeset.
* sites/staging/docs/release-notes/1.11.html

(github-issue): Document compatibility problems between Github and SVN 1.11.

In 'staging': update the 'Supported Versions' table for 1.11.
In 'staging': add date of 1.11 release; remove from 'upcoming releases' table.
  1. … 1 more file in changeset.