How Stable Grimoire is Updated Between Regular Updates

See Stable_Grimoire_Bug_Handling

How Stable Grimoire is Updated Regularly

  1. On the 1st of each month, the grimoire version currently in the test (master) branch is branched to the next stable-rc:

    1. git checkout -b stable-rc-$STABLE_RC_VERSION master

    2. sed -i 's/-test/-rc/' VERSION

    3. git commit -m "VERSION: $(cat VERSION)" VERSION

    4. git push origin stable-rc-$STABLE_RC_VERSION:refs/heads/stable-rc-$STABLE_RC_VERSION

  2. At the same time, test gets its VERSION incremented as well; normally this means bumping the minor version; major version updates are at the discretion of the Grimoire Lead:

    1. git checkout master

    2. sed -i 's/$OLD_TEST_VERSION/$NEW_TEST_VERSION/' VERSION

    3. git commit -m "VERSION: $(cat VERSION)" VERSION

    4. git push origin master

  3. A new wiki page is created for the new release by using http://wiki.sourcemage.org/StableReleaseTemplate to make http://wiki.sourcemage.org/Stable-$STABLE_RC_VERSION

  4. The release testing proceeds as described on the release wiki page, with the following additions:
    1. The target release date is the 15th of the month.
    2. The -rc branch must be frozen for 72 hours before it can be released as stable. This means no new commits on this branch. Exceptions are security updates and any other commits which meet the criteria for an out of cycle stable update, since they are already in stable anyway.
    3. Regardless of any updates run prior to the freeze, during the freeze period those who are able should run system-updates and/or full rebuilds using the stable-rc candidate and note any remaining or newly introduced gating bugs.
  5. When the release is complete, the new stable is branched from stable-rc:

    1. git checkout -b stable-$STABLE_RC_VERSION origin/stable-rc-$STABLE_RC_VERSION

    2. sed -i 's/-rc/-0/' VERSION

    3. git commit -m "VERSION: $(cat VERSION)" VERSION

    4. git push origin stable-$STABLE_RC_VERSION:refs/heads/stable-$STABLE_RC_VERSION

  6. A release tag and tarball are generated as described in http://wiki.sourcemage.org/Grimoire/Update_Tarball

  7. After the release, any FIXED bugs against this stable-rc or the previous stable need to be CLOSED.
  8. If the new release is not done when the 1st of the next month arrives, that branch is abandoned and a new -rc is created and the process starts over.

CategoryStableRelease

StableGrimoireUpdate (last edited 2009-02-02 17:08:30 by ArwedVonMerkatz)