Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 189 Next »

Release Management

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.

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 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.
Supported Releases

Version

Current Release

Release Date

Maint. Branch

Sakai 2.6

2.6.1

15 Oct 2009

2.6.x

Sakai 2.5

2.5.5

23 Jul 2009

2.5.x

Version

Current Release

Release Date

Maint. Branch

Kernel 1.1

1.1.0-beta03

17 Oct 2009

 

Kernel 1.0

1.0.12

12 Oct 2009

 

Unsupported Releases

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

Version

Final Release

Release Date

Maint. Branch

Sakai 2.4

2.4.1

21 Sep 2007

2.4.x

Sakai 2.3

2.3.2

21 Sep 2007

2.3.x

Sakai 2.2

2.2.3

12 Feb 2007

2.2.x

Sakai 2.1

2.1.2

12 Apr 2006

2.1.x

Sakai 2.0

2.0.1

16 Aug 2005

 

Sakai 1.5

1.5.1

27 May 2005

 

Sakai 1.0

1.0.0

18 Sep 2004

 

Release Management

Links to documentation describing important aspects of Sakai's Release Management 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 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.
    • Kernel 1.1.0 - Sakai Kernel 1.x release in support of Sakai 2.7, including new features and enhancements since Kernel 1.0; tentatively planned for mid-2009.
      *
    • Sakai 3.0 (3akai) - Official release 2011?
    • Sakai Roadmap - general timeline of ongoing or planned functionality enhancements and additions.

(For past releases we welcome volunteers from the community who are still using those releases to participate in a branch management team that will carry-on active management for that version, applying bug fixes, etc. If you're interested, please contact Anthony Whyte.)

  • No labels