Sakai 2.6.x Maintenance Branch
Official Release Page
The Official Sakai Release Page is the place to download the latest recommended version of the release, find installation and configuration documentation, etc.
Sakai 2.6
General Information
Branch Manager(s): Former user (Deleted), Former user (Deleted), Former user (Deleted), Former user (Deleted), Former user (Deleted)
Questions on the maintenance branch? Email sakai-dev@collab.sakaiproject.org.
Sakai 2.6.x Maintenance Branch
Appropriate bug fixes (no new features) are being merged from trunk to the 2.6.x Maintenance Branch. At periodic intervals, Maintenance Releasesare created from the Maintenance Branch. So you are encouraged to treat the most recent Sakai 2.6 Maintenance Release as the recommended version of Sakai 2.6. All fixes are must be tested prior to being merged into the branch, providing an additional layer of assurance. This branch will form the basis for #Sakai 2.6 Maintenance Releases.
Maintenance releases will be tagged from the 2.6.x Maintenance Branch at periodic intervals for up to two years after the initial release of Sakai 2.6.0 (or longer, if there is sufficient community interest and resources.)
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.6.x maintenance branch, then you need to determine which scripts are applicable based on your current revision of 2.6.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.6.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-6-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_6_0-2_6_x_<db>_conversion001_SAK-16668.sql |
-
SAK-16668Getting issue details...
STATUS
assignments / private notes and model answers does not display proper error message for text over 255 characters |
sakai_2_6_0-2_6_1_<db>_conversion.sql |
|
sakai_2_6_0-2_6_x_<db>_conversion002_SAK-16548.sql |
-
SAK-16548Getting issue details...
STATUS
Incorrect internationalization showing the grade NO GRADE |
sakai_2_6_0-2_6_1_<db>_conversion.sql |
|
sakai_2_6_0-2_6_x_<db>_conversion003_SAK-16847.sql |
-
SAK-16847Getting issue details...
STATUS
Make sure new asn.share.drafts permission is installed |
sakai_2_6_0-2_6_1_<db>_conversion.sql |
|
sakai_2_6_0-2_6_x_<db>_conversion004_SAK-10512.sql |
-
SAK-10512Getting issue details...
STATUS
-
SAK-17061Getting issue details...
STATUS
Backfill profile records with setting for new LOCKED column |
sakai_2_6_0-2_6_1_<db>_conversion.sql |
|
sakai_2_6_0-2_6_x_<db>_conversion005_SAK-14482.sql |
- SAK-14482Getting issue details... STATUS Mercury site has old assignments tool |
sakai_2_6_2-2_6_3_<db>_conversion.sql |
|
sakai_2_6_0-2_6_x_<db>_conversion006_SAK-8421.sql |
- SAK-8421Getting issue details... STATUS Statistics page is very slow |
sakai_2_6_2-2_6_3_<db>_conversion.sql |
|
sakai_2_6_0-2_6_x_<db>_conversion007_SAK-5742.sql |
- SAK-5742Getting issue details... STATUS create SAKAI_PERSON_T indexes |
sakai_2_6_2-2_6_3_<db>_conversion.sql |
There is no conversion script associated with 2_6_1-2_6_2
sakai.properties changes
- 2.6.1 - None