Actions

Difference between revisions of "Developer Area/Release Instructions/Old Major Release"

From Mahara Wiki

< Developer Area‎ | Release Instructions
(bumping the version on master)
(bump stable version on mahara.org)
Line 12: Line 12:
  
 
* Go to the master branch and bump the version to 1.5.0dev (if you just created the 1.4_STABLE branch)
 
* Go to the master branch and bump the version to 1.5.0dev (if you just created the 1.4_STABLE branch)
 +
 +
= Bump the stable_version on mahara.org =
 +
 +
(This is what sets the right download link in the header.)
 +
 +
Here's what I added in <tt>htdocs/local/upgrade.php</tt> for the 1.4 release:
 +
 +
if ($oldversion < 2011061501) {
 +
    set_config('mahara_stable_version', '1.4');
 +
}

Revision as of 17:49, 15 June 2011

Here are the things to do before running through the usual release instructions when preparing a new major release.

Major releases should be preceded by at least one release candidate.

Creating the new branch

  • Create a new branch in the admin section of Gerrit
  • Copy the changelog from the previous stable branch
  • Update the branch name in the "push" target of the Makefile

Bump the version on master

  • Go to the master branch and bump the version to 1.5.0dev (if you just created the 1.4_STABLE branch)

Bump the stable_version on mahara.org

(This is what sets the right download link in the header.)

Here's what I added in htdocs/local/upgrade.php for the 1.4 release:

if ($oldversion < 2011061501) {
    set_config('mahara_stable_version', '1.4');
}