My pages	Projects	Community	openCollabNet

Project tools

Project home

Membership

Getting Subclipse

Project Management

Additional Resources

Commercial support

How do I...

Category	Featured projects
scm	Subversion, Subclipse, TortoiseSVN, RapidSVN
issuetrack	Scarab
requirements	xmlbasedsrs
design	ArgoUML
techcomm	SubEtha, eyebrowse, midgard, cowiki
construction	antelope, scons, frameworx, build-interceptor, propel, phing
testing	maxq, aut
deployment	current
process	ReadySET
libraries	GEF, Axion, Style, SSTree
Over 500 more tools...

Subversion and IDEs
Eclipse
JDeveloper
NetBeans
Visual Studio

Subclipse Roadmap

This page contains information on past, current and future Subclipse releases as well as the process we follow to produce our releases.

How We Manage Releases

Subclipse follows an odd/even release strategy. So as an example, the 1.1.x and 1.3.x releases are "developer" releases for people that want to test the latest features. These culminate in 1.2.x and 1.4.x releases that will be the official "stable" releases. We do this so that we can use the Eclipse update site mechanism to easily deliver our developer releases to the users that want to use them. Historically the developer releases have been very stable and when problems do arise they are fixed quickly.

Current Releases

Release	Date	Eclipse Version	Subversion Version	Details
1.0.0	2006-04-11	3.0 - 3.1	1.4.x	changelog
1.2.0	2007-02-13	3.2+	1.4.x	changelog open issues
1.4.0	in development	3.2+	1.5.x	all issues

The above table shows the initial release date for each Subclipse stable release as well as the minimum Eclipse version supported and the version of Subversion that is required and currently included in the latest version in that release line. The Eclipse version will never change once a release is issued (1.0.x releases will always support Eclipse 3.0). As new versions of Subversion are released we typically issue new point releases that include support for that version of Subversion (Subclipse 1.0.0 included Subversion 1.3.x but Subclipse 1.0.4 added support for Subversion 1.4.x). Once we move to a new version of Subversion we can no longer support the older versions.

Upcoming Releases

Here is some information on future releases.

Next Release: 1.4.0

Development is underway on the 1.4.0 release. This release will be focused on Subversion 1.5 support and will be released soon after the Subversion 1.5.0 GA which should happen in mid-late summer 2007. Subversion 1.5 contains a number of new and exciting features including a number of enhancements that were specifically targeted at improving Subclipse and other IDE integrations. We will get a release out quickly that leverages many of these features and then continue to issue point releases throughout the year that adds additional support for these new features.

Use the following issue tracker query to get an idea what will be in the 1.4.0 release.

All Issues for 1.4 Release

Obviously items that are completed will be included in the release, open items are tentatively planned for the release but may not be included depending on the timeline of when Subversion 1.5.0 release. Subclipse 1.4.0 release date will be driven by the Subversion release date more than it will be driven by the features we have completed. This is because there will be a number of "free" improvements we get just by using 1.5. We will issue more frequent point releases as we add additional improvements.

Beyond the Next Release

Subclipse is a mature and stable product that supports all Subversion features. Future releases will focus on improving usability. For example making sure that dialogs can be controlled via keyboard only, general look and feel issue of dialogs etc. Of course there are always new Subversion features to add support for and we will always give those high priority.

Another goal in the upcoming releases will be better support for multi-project operations. This could be classified as a usability improvement, but it is such an important usability issue it deserves to be called out and brought into focus. Operations like branch/tag, merge and switch need to be enhanced so that they can be performed on multiple projects at the same time.