= Release strategy =
|| '''Date''' || 2010/04/27 ||
|| '''Contact(s)''' || Francois ||
|| '''Last edited''' || [[Timestamp]] ||
|| '''Status''' || ||
|| '''Assigned to release''' || None ||
|| '''Resources''' ||  ||

== Overview ==

Current release strategy is described here : [wiki:release_strategy].


But some points need clarification: 
 * We don't have automatic build system (Maven proposal will help to do automatic build but we don't have it yet).
 * Where to annouce stable/"unstable" release ? Which audience ? 
 * Where to release stable/"unstable" release ?
 * When is "unstable" release made ? time or feature based strategy ? no RC cycle.
 * What's an "unstable" release ? alpha release


This proposal aims to add details on the release process; mainly for "unstable" release (called "alpha release" later in that proposal).
The idea is to publish alpha release to a clearly identified audience (devel mailing list only and published in a separate folder on sourceforge).
Alpha release are created on a feature based strategy when major proposals have been added to trunk. This allows users to test new features without running GeoNetwork from source.
Alpha release are based on trunk and can be unstable.


=== Proposal Type ===
 * '''Type''': project governance
 * IRC discussion :
  * http://logs.qgis.org/geonetwork/%23geonetwork.2010-04-27.log


== Proposal ==

Release strategy for stable release:
 * Stable releases are created on a time schedule: every six months
 * Stable releases are using even numbered branch created from trunk on code freeze (version RC0)
 * Release Candidate 1 is built two weeks after RC0
 * Release Candidate 2 is built two weeks after RC1
 * Final Release is built two weeks after RC2
 * Stable releases are published in the main "!GeoNetwork_opensource" folder in sourceforge
 * Stable releases are announced on user and devel mailing lists

The Project Steering Committee (PSC) can postpone a stable release by vote on the mailing list.

Between two stable releases, one or more alpha releases could be created. Alpha release can be unstable.

Release strategy for alpha release:
 * Alpha releases are created on a feature based strategy : after major proposals have been added to trunk
 * Alpha releases are based on trunk and are built with uneven version numbers
 * Alpha releases are published in the "!GeoNetwork_opensource_alpha" folder
 * Alpha releases are announced on devel mailing lists only

Fixes are committed to both trunk and even numbered branch

For releasing files on sourceforge.net :
 * follow [http://apps.sourceforge.net/trac/sourceforge/wiki/Release%20files%20for%20download these instructions] (release manager only)