mahara-contributors team mailing list archive

[Mahara Bot <988682@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://reviews.mahara.org/1169
Committed: http://gitorious.org/mahara/mahara/commit/ab160d78817c52016d1b4319f59a4ab3e656ea89
Submitter: Hugh Davenport (hugh@xxxxxxxxxxxxxxx)
Branch:    master

commit ab160d78817c52016d1b4319f59a4ab3e656ea89
Author: Richard Mansfield <richard.mansfield@xxxxxxxxxxxxxxx>
Date:   Thu Apr 26 16:41:00 2012 +1200

    Change version of safe iframe sources upgrade (bug #971282)
    
    We have just committed to master a database upgrade with a version
    number less than the current version number of the 1.5 branch.  This
    means that an upgrade from the current 1.5 to master will not add the
    safeiframe tables.
    
    This patch changes the version number on master to ensure the upgrade
    is applied.
    
    This occurred because the 1.5_STABLE branch's version leapfrogged over
    the master version during the release candidate stage.  This will be
    fixed in the release script (see bug #988682).
    
    Change-Id: Ic2929fa9f17719a6068494ab63e7f00558c2fdcc
    Signed-off-by: Richard Mansfield <richard.mansfield@xxxxxxxxxxxxxxx>

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
https://bugs.launchpad.net/bugs/988682

Title:
  Release script fails to increment version correctly for release
  candidates

Status in Mahara ePortfolio:
  Triaged

Bug description:
  The release.sh script tries to bump version numbers by one on stable
  releases, and using the current date on unstable releases from the
  master branch.  It should be changed to increment by one on any stable
  branch, for rc releases as well as official releases, because
  otherwise the stable version can go higher than the master version,
  and we run the risk of some upgrades not being applied.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/988682/+subscriptions