Last revised January 2010
The most current release is Sakai 2.6.0, which was released on July 23, 2009. See the announcement at the announcements maillist archive. The first maintenance release for 2.6 (which will be 2.6.1, natch) should be available in the second half of September 2009.
QA testing for Sakai 2.7.0 is underway. The set of new tools and capabilities in 2.7 include:
- Site Stats
- Profile 2
- Basic LTI
- Conditional Release
- Messagecenter UX improvements
Research and Development work for a new generation of the product, Sakai 3, is fairly well along. Although we are some time yet from a full Sakai 3.0 release, Sakai 3 code should begin to appear in some production instances by mid-2010. See below for more details.
Sakai 2.7.0 is expected to be released in April 2010.
Sakai 2.6 separated out key back-end services into an independent kernel, termed 'K1.' The aim was to provide a more stable, better organized framework against which to build tools, and to allow the framework and tools to evolve on separate time-scales from functional releases.
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
Sakai 3 represents a rewrite of the Sakai framework, both technically and as a reimagined user experience. Its first set of designs came out of the UX initiative, and its early development has been led by Cambridge. A second UX design phase started in September of 2009, and will culminate in a milestone to be ready for QA by April 2010.
Sakai 3 (S3) development is a distributed effort with many moving parts. Efforts going toward Sakai 3 fall into 3 categories.
Efforts to inform S3
A. Functional Visioning
- Teaching and Learning
- OSP vignettes
B. User Research
- Learning Capabilities
Efforts to deliver S3
These are the efforts to design and code the core product, from the UX framework to the back-end.
Efforts to build on S3
There are also some early development projects that expect to make use of S3 at some point in future, although S3 is not yet in a deployable state.
- K2: a new set of core services at the back end (K2 stands for "Kernel 2").
- 3akai: a new UX framework; an HTML/CSS and JS front-end which implements a new design in an accessible way.
- Groups: a design-led effort focused on the full variety of ways in which groups are used in academic settings and how Sakai can be used to organize one's experience of them.
The first deployable milestone should be ready for QA by April 2010. This first production milestone should establish a new UX framework for Sakai and begin to offer new capabilities for sharing content, authoring pages and workspaces, and setting up simple groups outside course and site contexts. The latest state of the development work can be experienced directly at http://3akai.sakaiproject.org/dev.