This is a preliminary timetable for the next few upcoming releases. As noted above, we do not guarantee that a specific feature will be in a given release, or that a release will be published on a particular schedule. The following chart is more of a guideline for the developers to help ensure more timely releases, and is quite mutable.
| Date | Task | Notes |
|---|---|---|
| January 28, 2009 | Branch 1.6.x, roll 1.6.0-rc1 | |
| February 25, 2009 | Roll 1.5.6 release | This date may change, depending on the 1.6.0 release schedule. |
| Late February 2009 | Roll 1.6.0 tarball |
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 typical nomination/review/vote/merge process in the couple of days prior to the release, and it also allows some time for committers to test and sign the tarball before the weekend hits. The release is finalized and announced shortly after all the signatures are collected. See the release process for more information.
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 Hacker's Guide to Subversion.
We try to have at least one or two new features under active development at any given time, but we generally don't rush a feature to get it into a release. The flexibly time-driven model described above means there's never a long wait between releases, which in turn means less pressure to cram a feature into whatever release happens to be going out the door next. Our main source of ideas is our users: we watch the users@subversion.tigris.org mailing list, the #svn IRC channel, and the issue tracker to see what people are saying, and base our priorities on that, though we may sometimes grab low-hanging fruit along the way.
Below are new features currently under discussion and design, as extracted from the ever-changing consensus of the Subversion developer community. Because this is a volunteer open-source project, it's hard to predict exact dates or timetables for these new features. At most, we can express dependencies and predict the order in which things will be worked on. Just because a feature is listed for a particular release does not guarantee that it will be in that release. Hard feature lists don't actually get set until the release branch is created. The best way to track development is to subscribe to the development mailing list, dev@subversion.tigris.org.
hybrid distributed/centralized VC model
repository-level ACLs
broader WebDAV/deltaV compatibility
improved pluggable client-side diff (see issue #2044)
progressive multi-lingual support
SQL repository back-end?
For information about past releases, see the release history.
To see a summary of the major changes in each Subversion release, read over the CHANGES file.