Currently undergoing some revision
Help Keep the Roadmap Up-To-Date!
If you have updated planning information to share, comment on this page. Thanks.
Release management planning for 2.7 is underway, and there will be a code freeze data at some point in September. The set of new features expected to be in 2.7 are now being reviewed: Proposed Sakai 2.7 Changes
Research and Development work for a new generation of the product, Sakai 3, is fairly well along. This work so far includes a new kernel based on Apache Sling and a new UX framework that grew out of the UX initiative. Cambridge and Georgia Tech expect to be able to deploy the earliest milestone of this work to their campuses near the end of 2009, though it will not yet be ready for a full Sakai release.
The current release in the Sakai 2.x series is Sakai 2.6.0.
The goals for Sakai 2.7 are:
- Refinements and bugfixes for existing core tools, especially where they offer an improved User Experience. No major new tools or entirely new sets of capabilities
- Release by the end of 2009
Proposed Sakai 2.7 Changes are being collected and will be reviewed by a process that includes a release management team, the product manager, and the Product Council.
The full list of Jira Tasks scheduled for Sakai 2.7.
The initial vision for the Sakai 3.x series is still coming together. An early look at this work as evolves can be found on this demo server:
Tentative goals for Sakai 3.x are listed below, however, please keep in mind this is a work-in-progress:
- Significant improvements in the user experience, drawing heavily on Web 2.0 thinking, such as dashboards, widgets, gadgets, drag-and-drop support, etc.
- Content authoring and organization capabilities to provide more flexibility in populating and organizing sites.
- Expansion of permission scope beyond the current site-exclusive-basis.
- Better cross-tool workflow and integration.
- Add social networking capabilities.
- Ease of development through improved separation of concerns between java developers, java script programmers, and user experience designers.
- Improved scalability and robustness.
- Decreased production complexity and resource requirements.
- Simplified installation and expansion requirements.
These goals are further described in a Sakai 3 Proposal document.
With the release of Sakai 2.6 key, supporting, back-end services were separated out into an independent kernel project, Kernel 1 (or K1). This was done in part with the longer term goal of providing a more stable, better organized framework against which to build tools, and to allow the framework and tools to evolve on separate time-scales. This separation was a key step on the way to rethinking kernel services for Kernel 2.
The goals for the Kernel 1.0.x series are:
- Bug-fixing in support of Sakai 2.6.x through early 2011.
- Kernel 1.0.0 Jira Roadmap
- Kernel 1.0.x Jira Roadmap
- Kernel 1.0.1 Jira Roadmap
The goals for the Kernel 1.1.x series are:
- Bug-fixing and minor improvements in support of the Sakai 2.7 series through early 2012.
- Ability to cluster-enable Sakai to support session fail-over using Terracotta ( - SAK-13324Getting issue details... STATUS )
- Kernel 1.1.0 Jira Roadmap
Most of the information on Kernel 2.x can currently be found here.
The goals for the Kernel 2.x series are:
The Sakai 3.x series will eventually switch from being based on Kernel 1 to Kernel 2 in early- to mid- 2009. Sakai 2.x will not make use of Kernel 2 services, and will remain base on Kernel 1 services; however, much of the functionality of Sakai 2.x will initially be made available in Sakai 3.x through a compatibility approach.