Sakai 2.5.x Maintenance Branch

General Information

/wiki/spaces/ARCHIVE/pages/19428639086

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
  • Candidate fixes for merging to 2.5.x (
    

    type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

    )
    
  • Fixes merged to 2.5.x since last Maintenance Release (
    

    type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

    )
    
  • 2.5.x issues updated in the last 24-hours (
    

    type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

    )
    
• 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.

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

---

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.

---

Sakai 2.5.1 Maintenance Release

DB Schema Changes

There were db conversion scripts for this release, however, with the discontinuation of this release they were moved forward to the 2.5.2 release and renamed. See #Database Schema Changes above for more information.

sakai.properties Changes

None.

---

Sakai 2.5.2 Maintenance Release

DB Schema Changes

The 2.5.2 db conversion scripts are the same as those for 2.5.1, which was discontinued before being officially released, and were simply renamed to reflect the fact folks will be stepping from 2.5.0 directly to 2.5.2 during upgrades (and skipping 2.5.1):

sakai_2_5_0-2_5_2_<db>_conversion.sql

See #Database Schema Changes above for more information.

sakai.properties Changes

• Sakai 2.5.0 and earlier used the following properties for the WebDAV authentication cache:

  maximumSize@org.sakaiproject.user.impl.AuthenticationCache
  timeoutMs@org.sakaiproject.user.impl.AuthenticationCache
  failureThrottleTimeoutMs@org.sakaiproject.user.impl.AuthenticationCache
  

  These settings have been replaced as of Sakai 2.5.2 with:

  maxElementsInMemory@org.sakaiproject.user.api.AuthenticationManager.cache
  timeToLive@org.sakaiproject.user.api.AuthenticationManager.cache
  

Fixes

• Sakai 2.5.2 Fixes (
  

  type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  )
  

---

Sakai 2.5.3 Maintenance Release

DB Schema Changes

sakai_2_5_2-2_5_3_<db>_conversion.sql

See #Database Schema Changes above for more information.

sakai.properties Changes

None.

Fixes

• Sakai 2.5.3 Fixes (
  

  type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  )
  

---

Sakai 2.5.4 Maintenance Release

See 2.5.4 Maintenance Release.

---

Sakai 2.5.5 Maintenance Release