Currently undergoing some revision
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 broader goals for 2.7 are:
1) A simple, measured introduction to a new set of product development processes
- Provide the new Product Council space and time to work with development teams around significant new functionality
- Avoid unnecessary disruption to the momentum of development work to date
2) A reliable, published release roadmap
- A clear plan before QA begins
- A plan designed around meeting the broadest user needs with the highest quality code while minimizing risk to target timelines
The specific priorities for achieving these goals are:
1) Release by the end of 2009
2) Refinements and bugfixes for existing core tools (i.e. those already in 2.6), especially where they offer an improved User Experience. No major new tools or entirely new sets of capabilities
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 broader goals and specific aims for 2.8 will be:
1) Significant new functionality vetted by emerging Product Council processes, including the formulation of criteria in coordination with development teams and community discussion.
2) Release by May of 2010
The significant new functionality being considered is presently also being collected among Proposed Sakai 2.7 Changes.
Tentative goals for Sakai 3 are listed below
- 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:
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.
Associated Projects' Roadmaps
Last revised June 2014
Sakai Project Timeline 2008-Present
(Interactive - Full events link)
- Sakai CLE
The most current release is Sakai 10, which was released on June, 2014.
Sakai generally maintains both the current major release and the prior one - which is now Sakai 2.9. However generally only critical bugs and security fixes are maintained in a previous release and in the maintenance release branch. It's generally recommended to upgrade to the newest version of Sakai shortly after it's released
Sakai 2.9 was released in 2013 and is currently in maintenance mode.
The major set of new tools and capabilities in 2.9 include:
For full details please see the TCC voting summary