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.
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.
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: ------------------------------------------------------------------------ r1922447 | svn-role | 2024-12-12 04:00:07 +0000 (Thu, 12 Dec 2024) | 9 lines Merge r1922418 from trunk: * r1922418 Restore swig-rb to be compatible with Ruby 1.9 through 2.2. Justification: Fix incompatible with old versions of Ruby in 1.14.5. Votes: +1: jun66j5, futatuki ------------------------------------------------------------------------ r1924122 | dsahlberg | 2025-03-01 22:56:42 +0000 (Sat, 01 Mar 2025) | 15 lines Try to get the backport conflict detection GitHub Action working. It was suggested in the #asfinfra Slack channel[1] that workflows must exist in all branches to work so let's try to add them. Technically merging all revisions affecting the .github/ subtree from trunk. * .github/ Add subtree (This commit technically breaks the backporting requirements, but it won't even distributed downstream so I'm bending the rules this time). [1]: https://the-asf.slack.com/archives/CBX4TSBQ8/p1740835005043529 ------------------------------------------------------------------------ r1924124 | dsahlberg | 2025-03-01 23:04:33 +0000 (Sat, 01 Mar 2025) | 4 lines Followup to r1924122 Merge r1924123 from trunk, adding the subversion package on the GHA runner ------------------------------------------------------------------------ r1924127 | dsahlberg | 2025-03-01 23:16:17 +0000 (Sat, 01 Mar 2025) | 4 lines Followup to r1924124 and r1924122 Merge r1924125 from trunk, switching to a proper SVN WC ------------------------------------------------------------------------ r1924794 | svn-role | 2025-04-05 04:00:06 +0000 (Sat, 05 Apr 2025) | 10 lines Merge r1924100 from trunk: * r1924100 Deprecate and disable the SVN_UNALIGNED_ACCESS_IS_OK macro. Justification: Prevent future problems on newer compilers on higher optimization settings. Votes: +1: dsahlberg, brane, jamessan ------------------------------------------------------------------------ r1924795 | svn-role | 2025-04-05 04:00:13 +0000 (Sat, 05 Apr 2025) | 10 lines Merge r1924143 from trunk: * r1924143 Remove optimized unaligned-access code paths. Justification: Prevent future problems on newer compilers on higher optimization settings. (Follow-up to r1924100) Votes: +1: dsahlberg, brane, jamessan ------------------------------------------------------------------------ r1924796 | svn-role | 2025-04-05 04:00:20 +0000 (Sat, 05 Apr 2025) | 9 lines Merge r1924773 from trunk: * r1924773 swig-rb: Support ruby x64-mswin64 and building with GCC 15. Justification: Allow swig-rb with x64-mswin64 and gcc 15 Votes: +1: jun66j5, jamessan ------------------------------------------------------------------------
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.
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.13.x and earlier | No longer supported |