Context Navigation

Version 5 (modified by fxp, 14 years ago) ( diff )
--

Release strategy

Current release strategy is described here : 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 try to add some details on the release process; mainly for "unstable" release (called "alpha release" later in that 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 :

Note: See TracWiki for help on using the wiki.