Apache Subversion Releases

New 6-month regular and 2-year LTS release schedule: see How We Plan Releases.

The Apache Subversion project publishes releases with a relatively high degree of regularity. At any given time, we're working towards our next major release while continuing to fix bugs in previous releases. Subversion's release compatibility promises make adoption of our bugfix releases easy — you'll find very few, if any, surprises in those kinds of releases in terms of features and functionality. As such, the release notes issued for a given major release (an X.Y.0 release) remain applicable for patch releases to that release line (an X.Y.Z release). You can find links to these release notes below.

Over time and as new major releases come out, we drop official support for older release lines. You'll also find below the project's official support status for the various release lines available.

Release Notes

Here are the release notes for the major Subversion releases:

For a more complete (albeit less descriptive) list of changes made in individual releases, see the CHANGES file.

For a detailed history of every release, please see release history.

Coming up in the next patch release

The following changes have been merged since the last patch release and will almost certainly be included in the next patch release:

Changes in ^/subversion/branches/1.14.x:
r1904478 | svn-role | 2022-10-10 04:00:03 +0000 (Mon, 10 Oct 2022) | 10 lines

Merge r1904472 from trunk:

 * r1904472
   swig-rb: Use Ruby API 'File.exist?' instead of deprecated 'File.exists?'
     Deprecated API 'File.exists?' is deprecated as of Ruby 2.1 and removed
     as of Ruby 3.2.
    +1: hartmannathan, dsahlberg

r1905107 | svn-role | 2022-11-07 04:00:02 +0000 (Mon, 07 Nov 2022) | 15 lines

Merge r1900882 from trunk:

 * r1900882
   SVN-4899: Replace a call to a function deprecated upstream.
     No-op on Python 3.2 and newer, but will allow Subversion 1.14.x to be
     built by future Python 3.12.  Note that Python 3.2 was released 9 years
     before Subversion 1.14.0.
     +1: danielsh, jamessan
     -0: futatuki (This breaks Python 2.7 support;
                   +1 if r1900890 (see below) is also backported)

[ Editor's note: r1900890 got backported in r1905108. ]

r1905108 | svn-role | 2022-11-07 04:00:04 +0000 (Mon, 07 Nov 2022) | 12 lines

Merge r1900890 from trunk:

 * r1900890
   Follow up to r1900882: Restore Python 2.7 support on autogen.sh
     autogen.sh is need to build SWIG Python 2 bindings.
     We have not actively dropped Python 2.7 support, at least on 1.14.x.
     +1: futatuki, jun66j5, jamessan

r1905109 | svn-role | 2022-11-07 04:00:05 +0000 (Mon, 07 Nov 2022) | 10 lines

Merge r1904193 from trunk:

 * r1904193
   SVN-4908: Copy 'locked' from svn_wc_status3_t to svn_wc_status2_t
     Allow PySVN (and other deprecated API users) to detect working copy
     locked status.
     +1: hartmannathan, rhuijben, jamessan

r1905110 | svn-role | 2022-11-07 04:00:06 +0000 (Mon, 07 Nov 2022) | 9 lines

Merge r1904936 from trunk:

 * r1904936
   Add @Deprecated decorations to avoid compiler warnings.
     Avoid some compiler warnings
     +1: dsahlberg, jamessan

r1905111 | svn-role | 2022-11-07 04:00:07 +0000 (Mon, 07 Nov 2022) | 9 lines

Merge r1904938 from trunk:

 * r1904938
   Java binding fixes.
     Don't crash if someone uses a null message
     +1: dsahlberg, jamessan

r1905112 | svn-role | 2022-11-07 04:00:09 +0000 (Mon, 07 Nov 2022) | 10 lines

Merge the r1878379 group from trunk:

 * r1878379, r1883719, r1883722, r1884610
   Distinguish configure scripts on release mode and non release mode.
     Building process should not be prevented by swig installed in users'
     environment when users use release tar balls.
     +1: futatuki, stsp, jamessan

r1905172 | svn-role | 2022-11-09 04:00:03 +0000 (Wed, 09 Nov 2022) | 11 lines

Merge r1877310 from trunk:

 * r1877310
   Add a test for issue #4711 "invalid xml file produced by svn log --xml
   --verbose --use-merge-history --search".
     Increase test coverage.
     +0: danielsh (with appropriate Skip()/XFail() annotations if needed)
     +1: hartmannathan, jamessan

r1905173 | svn-role | 2022-11-09 04:00:04 +0000 (Wed, 09 Nov 2022) | 10 lines

Merge r1904167 from trunk:

 * r1904167
   swig-py: Fix conditionals by SWIG version and by Python version for proxy
     swig-py should be built correctly with upcoming SWIG 4.1.0 release.
     +1: futatuki, jun66j5, jamessan

r1905330 | svn-role | 2022-11-16 04:00:03 +0000 (Wed, 16 Nov 2022) | 12 lines

Merge the 1.14.x-r1903267 branch:

 * r1903267
   Makefile.in (fast-clean, clean-swig-py): Remove __pycache__ directory
   as well as *.pyc
     We don't want that the release tarballs contains extra directories.
     +1: futatuki, jamessan, rhuijben

r1905332 | svn-role | 2022-11-16 04:00:20 +0000 (Wed, 16 Nov 2022) | 11 lines

Merge the r1904198 group from trunk:

 * r1904198, r1904287
   swig-py: build: Don't pass deprecated options to SWIG >= 4.1.0 release
     Reduce extra deprecation warnings from SWIG.
     r1878379, r1883719, r1883722, r1884610
     +1: futatuki, jamessan, rhuijben


Further changes currently under consideration are listed in each release line's STATUS file.

See also trunk/CHANGES, where all significant-enough changes will summarized for each version by the time it is released.

The list above is generated daily by ^/subversion/site/tools/upcoming.py. 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.

Supported Versions

See How We Plan Releases for details of the release schedule and support levels.

Version Type of Release
1.14.x Long-Term Support
1.11.x - 1.13.x No longer supported
1.10.x Long-Term Support
1.9.x and earlier No longer supported