Sakai 2.5.x Maintenance Branch
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.
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.
Database Schema Changes
Schema changes are sometimes required to resolve bugs. Each time there is new DDL associated with a bug, the release manager will create a file that includes only the pertinent changes, and name it according to the pattern below. Each time there is a maintenance release, those files will be rolled up into conversion scripts for that release.
If your Sakai instance is based on releases, then all you need to do is run all intervening upgrade scripts. For instance, if you are upgrading from 2.5.1 to 2.5.4, then you need to run the 2.5.1-2.5.2, 2.5.2-2.5.3, and 2.5.3-2.5.4. (Note that not all releases will have upgrade scripts, as sometimes there are no db schema changes required.)
If your Sakai instance is based on a revision of the 2.5.x maintenance branch, then you need to determine which scripts are applicable based on your current revision of 2.5.x and the revision you wish to get to. The Subversion revision numbers in the table should help you identify which scripts you need to run.
If your Sakai instance is based on pulling patches selectively from 2.5.x, then you will need to manually determine which scripts are appropriate to run.
The individual script(s) are located in the source repository at: https://source.sakaiproject.org/svn/reference/branches/sakai_2-5-x/docs/conversion/, while the release roll-ups are included in the release itself.
Script ID | SVN Revision | Notes | Roll-up file for Sakai release |
|---|---|---|---|
sakai_2_5_0-2_5_x_<db>_conversion001_SAK-13643.sql | Fix tool placement for renamed Reports tool. | sakai_2_5_0-2_5_2_<db>_conversion.sql | |
sakai_2_5_0-2_5_x_<db>_conversion002_SAK-11130.sql | | sakai_2_5_2-2_5_3_<db>_conversion.sql | |
sakai_2_5_0-2_5_x_<db>_conversion003_SAK-13842.sql | | sakai_2_5_2-2_5_3_<db>_conversion.sql | |
sakai_2_5_0-2_5_x_<db>_conversion004_SAK-13474.sql | | sakai_2_5_3-2_5_4_<db>_conversion.sql | |
sakai_2_5_0-2_5_x_<db>_conversion005_SAK-14482.sql | | sakai_2_5_5-2_5_6_<db>_conversion.sql | |
sakai_2_5_0-2_5_x_<db>_conversion006_SAK-8421.sql | |
| |
sakai_2_5_0-2_5_x_<db>_conversion007_SAK-13345.sql | Missing index on search |
|
Originally there were sakai_2_5_0-2_5_1_<db>conversion.sql scripts, however, with the discontinuation of 2.5.1 prior to its release, those files become and 2_5_0-2_5_2<db>_conversion.sql scripts. (There were no db changes between 2.5.1 and 2.5.2.)
There is no conversion associated with 2_5_4-2_5_5
sakai.properties Changes
2.5.1 - none
2.5.2 - see below)
2.5.3 - none
2.5.4 - to be determined