We’ve had a Roadmap for a while, but it’s pretty simplistic, and I haven’t had enough of a plan to be able to reasonably maintain it.  In our call today, though, we came up with a pretty clear plan for what we’re going to do next, when we’re going to do it, and what version numbers it will have.  Here’s a summary of what we decided (which I’ll then be importing into the roadmap document, where it will actually be maintained).

• 0.24.7: We’re going to get this release out as soon as possible (most likely around the middle of November), with any critical fixes resulting from the 0.24.6 release.  This will be the last stable release in the 0.24.x line.
• 0.25: This release will be the first release from the master branch, and is planned for the end of the year.  Its primary changes will be all of the plumbing to support REST, plus converting, at a minimum, file serving and catalog retrieval to using REST.
• 0.26: This release will convert any remaining XMLRPC network APIs to REST, and will be the last release before 1.0. It should be out in the second quarter of 2009.
• 1.0: This release stabilizes the network API:  According to the plan, projects developed against its API should work going forward.

We’ve got less detail on the 2.0 and 3.0 releases, but we’ve got main targets for them.  The 2.0 release will focus on refactoring the transactional system, and the 3.0 release will focus on refactoring the RAL extension interfaces.

Now that we’ve got a version roadmap, we can begin doing realistic ticket assignments to those different versions.

Of course, we’ll still need a lot of help from the community to get all of the tickets done that we want to complete.  The versions will have a key deliverable, and that’s what I’ll be focusing on, but we’ll want a lot more in each release, and that’s where we’ll need help.