Sakai 2.5
Official Release Page
The Official Sakai 2.5 Release Page is the place to download the latest recommended version of the release, find installation and configuration documentation, etc.
Sakai 2.5
Pre-Release Information
General Information
Branch Manager(s): @Former user (Deleted), @Former user (Deleted), @Former user (Deleted), @Former user (Deleted), @Former user (Deleted), @Former user (Deleted), @Former user (Deleted), @Former user (Deleted), @Former user (Deleted)
Questions on the release? Email sakai-dev@collab.sakaiproject.org.
Appropriate bug fixes (no new features) are being merged from trunk to the 2.5.x Maintenance Branch. At periodic intervals, Maintenance Releases are created from the Maintenance Branch. So you are encouraged to treat the most recent Sakai 2.5 Maintenance Release as the recommended version of Sakai 2.5.
Jira Information
Some short-cuts to relevant views in Jira for Sakai 2.5-related information:
Filters
Statistics
Candidate fixes for merging to 2.5.x (count for Components by Priority)
Fixes merged since last Maintenance Release (count for Components by Priority)
Sakai 2.5.x Maintenance Branch
Only bug fixes are being merged to the Sakai 2.5.x Maintenance Branch, no new features are being introduced. This branch will form the basis for #Sakai 2.5 Maintenance Releases.
Sakai 2.5 Maintenance Releases
Maintenance releases will be tagged from the 2.5.x Maintenance Branch at periodic intervals for up to two years after the initial release of Sakai 2.5.0 (or longer, if there is sufficient community interest and resources.) The Maintenance Releases will include bug fixes merged from the Maintenance Branch for a selected subset of components, rather than all available fixes in the Maintenance Branch at that point in time the tag. Maintenance Releases will be subjected to a short period of focused QA, which will target the areas of change in the code. Only a selected subset of components is included in order to keep QA manageable and the interval between releases short. As a result, the Maintenance Releases will lag the Maintenance Branch in terms of completeness of fixes, however, this trade-off is important in enabling a high-frequency of well-tested Maintenance Releases.
Post-2.5 Feature Branches
Feature Branches are intended to provide early access to new functionality or enhancements intended for the next major release. This enables interested organizations to take advantage of the new functionality without waiting for the next release; however, the feature branches have generally only been subjected to limited QA by the project team itself, and they are typically offered on an as-is basis. (General information on Features Branches....)
For participating projects, the Feature Branch code is located in the post-2.5 branch in a project's SVN repository. The project may also provide tags, such as post-2.5-a, post-2.5-b, ..., to help identify reliable starting points from which to adopt the code.
For the Project Teams, part of the drive for this early delivery of functionality is to meet the needs of a team member's local Sakai implementation, hence, the functionality has typically been subjected to a good deal of testing at their institution and has generally been tested for production deployment. The Project Teams do not necessarily have additional time to incorporate others' design suggestions for the 2.6 release, however, they certainly will welcome bug reports and attempt to address them before the 2.6 release, and consider suggestions for future releases. Some Project Teams may also choose to continue supporting the post-2.5 branches with bug fixes even after 2.6 is released, but it is not guaranteed.
Projects tentatively planning to offer a post-2.5 Feature Branch include:
site-manage
- SAK-12868 - Getting issue details... STATUS: site templating
Email Service
- SAK-12581 - Getting issue details... STATUS: Add attachment support to Email service
Portal
Tests & Quizzes (a.k.a. Samigo)
Incorporating UCT's work on group-scoped tests and improvements to statistics reporting (
SAK-12065 - Getting issue details... STATUS).
Resources? and/or Content Hosting Service?