Tags:
create new tag
, view all tags

TWiki Release Manager Role

The roles of a release manager are to

  1. ensure that the release has good quality
    • by taking care that someone are addressing and closing the bugs
    • and that all urgent bugs are closed before final release
  2. ensure that all documentation is up to date (including upgrade guide and release note)
  3. ensure that unit tests are run, and failures are fixed quickly
  4. ensure that features are only added when agreed by TWikiReleaseManagementProcess
  5. build the releases - nightly, alpha, beta, rc and final - see BuildingARelease

For patch releases additionally

  1. Monitor bug fixes in the MAIN branch and arrange for the important bugfixes to be merged to current release branch
  2. Ensure that that only bug pure fixes are checked into the release branch and that they are of a nature that ensure on-the-fly upgrade of running installation.
  3. Creation of the changed package with only the changed files included

This is a floating role, as we may have a different release manager for each release. We may even have more than one at a time! See TWikiReleaseManagementProcess for more information on the role. Note that the release manager does not decide what is in and what is out. That authority belongs to the community and final decision in case of disagreement belongs to release meeting as described in TWikiReleaseManagementProcess.

Part of Task Summary Performed by
CoreTeamRoles Manages the mechanics of TWiki releases GeorgeTrubisky

Feedback and Comments

 
Topic revision: r20 - 2011-04-25 - GeorgeTrubisky
 
Twitter Delicious Facebook Digg Google Bookmarks E-mail LinkedIn Reddit StumbleUpon    
  • Download TWiki
TWiki logo Powered by PerlIdeas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2012 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.