Release Practices

Supported Releases

Support for releases is subject to the availability of community and volunteer resources to effect that support. Generally this will include the current release and prior releases for which there is a sufficiently large community of folks still running a particular release in production.

You are strongly encouraged to use or closely follow the maintenance branch for a release when running in production, as the Maintenance Branches provides access to important bug fixes. The project teams producing the fixes provide a minimal level of testing, however, a great deal of community QA is acheived for each fix by relying on the local QA processes of organizations preparing the fixes for deployment to production.

Maintenance Branches

Support for maintenance Branches is subject to the availability of community and volunteer resources to effect that support.

If you have a fix that you would like incorporated in a particular maintenance Branch, you need to contact the appropriate Project Lead or Branch Manager with your request. Comments in Jira asking for a fix to be merged will probably not be seen by the individuals who can do the merging. Also, do not add the maintenance branch as a fix version as a way of requesting a fix be incorporated; the fix version is used to reflect what versions the fix is actually in, and it will be set appropriately after a fix is merged into a maintencance branch.

Maintenance Branch

Branch Manager

Sakai 2.4.x Maintenance Branch

Andrew Poland

Sakai 2.3.x Maintenance Branch

Lance Speelmon

Sakai 2.2.x Maintenance Branch

Need a volunteer! (Contact Peter A. Knoop.)

Sakai 2.1.x Maintenance Branch

Brian Jorgensen