Sakai Release Process
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.
Use the Maintenance Branches
You are encouraged to run the maintenance branch for the release in which you are interested. The Maintenance Branches contain important bug fixes. Generally these fixes have not been subjected to the regular, formal QA processs, howver a number of organizations run the maintenance branch in production, thus providing limited QA.
- Next Release
- Sakai 2.4.0 is scheduled for Code Freeze on 15 March 2007 and release 01 May 2007.
- Past Major Releases
Support for maintenance Branches is subject to the availability of community and volunteer resources to effect that support.
Have a Fix for a Maintenance Branch?
If you have a fix that you would like incorporated in a particular maintenance Branch, you need to contact the appropriate Branch Manager with your request.
Comments in Jira asking for a fix to be merged will probably not be seen by the Branch Manager. 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.