Apache Subversion Roadmap

New 6-month standard and 2-year LTS release schedule

Upcoming Releases

The following is a preliminary timetable for the next few upcoming releases. 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!

Date Release Deliverables / Notes
2018-04-13 Release 1.10.0 LTS 1.10 release notes issue SVN-4712 "Release 1.10" downloads
2018-?? Release 1.10.1 maintenance...
2018-?? Release 1.9.8 security/corruption fixes...
2018-10 Release 1.11.0 better shelving, checkpointing, ...
2019-04 Release 1.12.0
2019-10 Release 1.13.0
2020-04 Release 1.14.0 LTS

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.

How We Plan Releases

Subversion makes a standard release every 6 months, with a Long-Term Support (LTS) release every 2 years:

type full backports security/corruption fixes release numbers
long-term support (LTS) 2 years 4 years 1.10, 1.14, ...
standard release 6 months 12 months 1.11, 1.12, 1.13, ...

LTS releases are intended to provide stability. Standard releases are intended to deliver new features more quickly.

Transition to LTS and Standard Releases

Subversion 1.0 through 1.10 were released at intervals varying from around 6 months in early versions to 2.5 years more recently. Each of those releases was supported with full backports until the next release and with security/corruption fixes until the next release after that.

The support schedule for existing supported releases (1.10 and 1.9) shall be interpreted as if each reference to a "next release" refers to a "next LTS release". Therefore 1.9 will receive security/corruption fixes until 1.14 LTS.

Previous Description

Subversion uses a compromise between time-driven and feature-driven release planning. We schedule the next release for an approximate date (very approximate), and make sure it contains one or more new features or other significant differentiators, but we don't say exactly what those new features will be. This is because we're always working on several things at once, and we want to give each new feature time to mature. Especially given the decentralized nature of open-source development, we're wary of forcing technical discussions to premature consensus. At the same time, it's good for the project to have regular releases, so we try to keep to a schedule and to have something ready to roll out when the release date comes along.

In this context, "release" means an increment of the minor release number, which is the middle number in our three-component system. Thus, 1.2.0, 1.3.0, and 1.4.0 are successive minor releases in the "1.x" line, whereas 1.1.1, 1.1.2, and 1.1.3 are successive patch (bugfix) releases in the "1.1.x" line. We don't schedule patch releases far in advance, we just put them out when we feel enough bugfixes have accumulated to warrant it. Major new releases, such as Subversion 2.0, will probably be done much like the minor releases, just with more planning around the exact features. 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.

Our "Most Wanted" Features

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.

Fill in the details here!

Feature / Enhancement Dependencies Target Release Issue(s)
Rename Tracking Ev2?, FS-NG? 2.0? 898, 3630
Improved Merging 1.x?
Improved Tree Conflict Handling Ev2, Rename Tracking 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

Next Release Status (Subversion 1.11)

For up-to-date information about the 1.11 release, please see the release notes.

The following table contains items currently targetted for the subsequent major release, along with their completion status. It is meant mainly for developers, but can help answer the oft-asked question "how is the next release coming along?" If you are interested in helping speed up the next release, consider tackling one of the incomplete items below.

This table is nonexhaustive — it neither contains nor attempts to contain all the features planned for this release.

Task Status Notes
Specific stuff aimed at this release
Commit shelving (improved since 1.10) In progress Issue 3625 Status in 1.11 will be "experimental".
Commit checkpointing In progress Issue 3626 Status in 1.11 will be "experimental".
Conflict resolver improvements In progress Ongoing improvements since 1.10.
Items originally planned for, but now deferred from, this release

Past Releases

For information about past releases, see the release notes.