At the moment, there is no timetable for the next release. Dates, feature deliverables, and even version numbers found in this list are all subject to change (and become increasingly more speculative the further out we attempt to project). Fortunately, the same dynamics that allow features to fall out of releases or for release dates to slip also allow for feature and release acceleration. That's the nature of open-source, community-driven software projects (and we think it's a great thing). So if you don't like what you see here, do something about it: your contributions are always welcome!
We try to roll releases on Wednesdays. Like most of the other information on this page, the day we roll isn't a hard-and-fast rule, but it is something that has been useful in the past. Rolling mid-week gives us enough time for the release preparation process in the couple of days prior to the release, and some time before the weekend for validation of the release tarballs. The release is finalized and announced as soon after the completion of the validation process as possible. See the documentation of our release process for more information.
Starting with 1.15, all release lines are supported for at least 3 years. At least one release line is always supported.
A release line becomes EOL when the following conditions are both met:
It has been supported for at least 3 years.
There is a new minor release line with an age of at least 6 months.
Among the supported release lines:
The latest release line ("N") receives full support.
Other release lines (N-1, N-2, …) receive security-only support and critical bugfixes, e.g., related to data corruption.
Previously Subversion differentiated between regular releases (supported for 6 months) and LTS releases intended to provide stability over longer periods (supported for 4 years).
Subversion 1.0 until 1.10 and 1.14 were LTS releases and 1.11, 1.12 and 1.13 were regular.
For more information about Subversion's release numbering and compatibility policies, see the section entitled "Release numbering, compatibility, and deprecation" in the Subversion Community Guide.
The following is a list of "most wanted" features/enhancements we've identified as important and achievable, in no particular order, along with the chain of dependendies we believe exist and stand in the way of our delivering these items in Subversion. This is not an exhaustive list! It merely represents some of the "the big ones" — big in impact, and probably big in development cost.
OUT OF DATE (written in 2010, only minor updates since then)
| Feature / Enhancement | Dependencies | Target Release | Issue(s) |
|---|---|---|---|
| Rename Tracking | Ev2?, FS-NG? | 2.0? | 898, 3630 |
| Improved Merging | 1.x? | ||
| Improved Tree Conflict Handling | 1.10 | ||
| Control of Strictness for Conflicts | 1.x? | 4405 | |
| Enterprise Authentication Mechanisms | 1.x? | 3629 | |
| Log Message Templates | Repository-dictated Configuration | 1.x? | 1973 |
| Shelve | 1.10 ... | 3625 | |
| Checkpoint | 1.11 ... | 3626 | |
| Flexible Repository Storage (FS-NG) | 2.0? | ||
| Obliterate | FS-NG | 2.0? | 516 |
| Forward History Searching | FS-NG? | 2.0? | 3627 |
Draft release notes are added to the release notes index some time before each release is published.
For information about past releases, see the release notes.