Skip to end of metadata
Go to start of metadata

 

Release Management

Sakai release support is subject to the availability of community and volunteer resources. Generally this will include the current release and prior releases for which there is a sufficiently large institutional user base. The Release Management Team maintains an email list at cle-release-team@collab.sakaiproject.org (mailto::cle-release-team@collab.sakaiproject.org)

Implementers are encouraged to deploy Sakai release tags or source or binary artifacts. A number of schools use maintenance branch code in production in order to pick up bug fixes as they become available. The project teams providing fixes provide a minimal level of testing, however, a great deal of community QA is achieved for each fix by relying on the local QA processes of organizations preparing the fixes for deployment to production. (See the Release Practice Guidelines for further information on how and what goes into these branches.)

Process and Practice

Links to documentation describing important aspects of Sakai's release management practices and processes:

  • Release Practice Guidelines - Community expectations and practices surrounding the management of the various Sakai release and branch types (i.e., Major Release, Maintenance Branches, Maintenance Releases, Jira Branches, Feature Branches, and Trunk). (See also Jira Guidelines.)
  • Security Guidelines - Our policy for reporting, handling, and resolving security related issues in Sakai.
  • Release Management Meetings - Generally weekly discussions of how work on releases and maintenance branches is proceeding.
  • Tool and Service Scorecards - A "Scorecard Working Group" formed to tackle the issue of how to improve upon the current Core/Provisional/Contrib Tool Status system and its criteria. The goal being a scorecard-like system to provide the release team with guidance on what to include in a release, and organizations deploying Sakai a comparative evaluation of tools' and services' capabilities.
Release Management Documents

Release Calendar
Commmunity-supported Releases

Version

Latest

Date

Issues

Maint. Branch

Sakai 2.8

2.8.2

04 Jun 2012

Jira

2.8.x

Sakai 2.7

2.7.2

13 Sep 2011

Jira

2.7.x

Starting with Sakai 2.6 low-level services have been repackaged as the Sakai "kernel" and are now released independently.

Version

Latest

Date

Issues

Maint. Branch

Kernel 1.2 (Sakai 2.8)

1.2.8

04 Jun 2012

Jira

 

Kernel 1.1 (Sakai 2.7)

1.1.10

7 Dec 2010

Jira

 

Unsupported Releases
These prior versions of Sakai are no longer supported or recommended for production use.     

Version

EOL

Final Release

Issues

Maint. Branch

Sakai 2.6

13 April 2011

2.6.3

Jira

2.6.x

Sakai 2.5

11 June 2010

2.5.6

Jira

2.5.x

Sakai 2.4

22 Jul 2009

2.4.1

Jira

2.4.x

Sakai 2.3

25 Mar 2008

2.3.2

Jira

2.3.x

Sakai 2.2

21 May 2007

2.2.3

Jira

2.2.x

Sakai 2.1

3 Nov 2006

2.1.2

Jira

2.1.x

Sakai 2.0

19 Jul 2006

2.0.1

Jira

 

Sakai 1.5

3 Jan 2006

1.5.1

Jira

 

Sakai 1.0

3 Jan 2006

1.0.0

 

 

 

Meeting Notes

Release Management meetings are generally held on a weekly basis to discuss on-going work on releases and maintenance branches. Discussion is also carried out between meetings on mailing lists, such as sakai-dev@collab.sakaiproject.org and sakai-qa@collab.sakaiproject.org. Meeting notes from past meetings are linked below.

Conference Calls

Anyone in the community is welcome to partipcate in the weekly calls.

Meeting Notes

Jira Issues