== Current release strategy ==
[wiki:release_strategy]

== Comments & new questions ==
 * We don't have automatic build system.
 * Where to annouce stable/"unstable" release ?
 * Where to release stable/"unstable" release ? Separate folders ?
 * What's an "unstable" release ? alpha release ?
 * When is "unstable" release made ?

== 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 annouced 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 after major proposals have been added to trunk (feature based strategy)
 * Alpha releases are based on trunk and are built with uneven version numbers
 * Alpha releases are published in the "Unstable_GeoNetwork_opensource" folder
 * Alpha releases are annouced 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)