Release guide

From MapbenderWiki

Contents 1 Kick-off 2 Discussion 3 Merging 4 Release branch 5 Update information 6 Testing 7 Compilation 8 Announcement 9 Update demo server 10 Stable / unstable

Kick-off

• Rule of thumb: Every three months a new version is released.
• If there are significant changes that cannot be finished in three months, the release may be delayed.
• The release owner announces plans for a new release at the developer list, along with
  1. suggestion release number
  2. suggestion release date
  3. suggestion of new modules

Discussion

• Discussion (approx. 1 week) at developer list about
  1. release number
  2. release date
  3. new modules
• Voting on the above (motioned by release owner)
• Feature freeze

Merging

• All new features that will be included in the release must be merged into the trunk.

Release branch

• A release branch is generated from the trunk.

Update information

• update Version History
• update Trac info
  1. add new version number
  2. add new reports

Testing

• During this phase, a lot of testing has to be done.
• Only bug fixes may be committed to the release branch after rc1!

Compilation

• How to compile a release
• The first release of a new version number must be a release candidate.
• If the previous release candidate is not stable, another release candidate follows.
• There is no maximum number of release candidates.
• Please note that the interval between first rc and stable version is not fix.

Announcement

• mapbender_dev@lists.osgeo.org
• mapbender_users@lists.osgeo.org
• News at Mapbender Wiki: http://www.mapbender.org/index.php/Template:News

Update demo server

• at http://mapbender.telascience.org/
• Done by the Mapbender Telascience administrators

Stable / unstable

If the release proves to be unstable, repeat the procedure starting from Update information

After a stable version has been released

• OSGeo announcements: email them to news_item@osgeo.org as described here.
• a new release owner might be elected