GeoMOOSE Logo
The Home of GeoMOOSE!
Home | Wiki | Live Demo | Getting Started | Documentation | Developers | Bug Tracker | Download

Table Of Contents

This Page

RFC 3: GeoMOOSE Release Process

Author:Eli Adam, (inspiration also from MapServer RFC 34)
Contact:eadam at ...
Status:development
Last Updated:05/08/2012

Summary

This document describes the GeoMOOSE Release Process. The purpose of the Release Process is to ensure that GeoMOOSE releases continue at a high quailty level. This is best accomplished through following a documented replicatable process. A Release Manager will be responsible for coordinating or implementing these details.

Details

  • GeoMOOSE releases will be made based on this RFC and GeoMOOSE How To Release.
  • GeoMOOSE releases start with a discussion and motion on the email list. This should cover an outline of the schedule, a feature list or freeze date, and nomination of a Release Manager.
  • The Relase Manager can update how_to_release.txt as needed over time.
  • The Release Manager is given wide latitude to make decisions pertaining to the Release Process.
  • The Release Manager can delegate parts of the process to others but must make sure that the work gets done.
  • The Release Manager should keep all informed of progress during the Release Process.
  • GeoMOOSE releases should be well tested, well documented, and well publicized.

Observations

  • Detailing the Release Process makes it possible for more people to help on releases.

  • GeoMOOSE version numbers have the following meaning.
    • Take the example: 2.0.1
    • The major version number is 2
    • The minor version number is 0
    • The revision number is 1
    • Major versions are infrequent and are the result of major architectural or functional changes. There will be more than 1 year between each major version and usually several years.
    • Minor versions are regular occurences. Minor versions only come in even numbers as formal releases (odd numbers being development versions that are not formally released). Minor versions are incremented with additions of functionality. Usually these additions are tracking the geospatial and web worlds, nothing groundbreaking.
    • Revisions are fixes to minor releases. Revisions only fix reported bugs and do not add functionality.

Voting History