| | 1 | == Current release strategy == |
| | 2 | Release strategy: |
| | 3 | * Stable releases are created on a time schedule: every six months |
| | 4 | * Release Candidate 1 is built two weeks after RC0 |
| | 5 | * Release Candidate 2 is built two weeks after RC1 |
| | 6 | * Final Release is built two weeks after RC2 |
| | 7 | |
| | 8 | The Project Steering Committee (PSC) can postpone a release by vote on the mailing list. |
| | 9 | |
| | 10 | Branch strategy: |
| | 11 | * Trunk is for development and is automatically built with uneven version numbers |
| | 12 | * Even numbered branch is created from trunk on code freeze (version RC0) |
| | 13 | * Automated builds based on trunk will use the next uneven version number immediately after code freeze |
| | 14 | * Fixes are committed to both trunk and even numbered branch |
| | 15 | * Release Candidates are built from the even numbered branch |
| | 16 | |
| | 17 | For releasing files on sourceforge.net follow [http://apps.sourceforge.net/trac/sourceforge/wiki/Release%20files%20for%20download these instructions] (release manager only) |
| | 18 | |
| | 19 | Uploading can be done through SCP with the following command: {{{scp FILE jsmith@frs.sourceforge.net:uploads}}} |
| | 20 | |
| | 21 | == Comments & new questions == |
| | 22 | * We don't have automatic build system. |
| | 23 | * Where to annouce even/uneven release ? |
| | 24 | * Where to release even/uneven release ? Separate folders ? |
| | 25 | * What's an "unstable" or alpha release ? |
| | 26 | * When is alpha release made ? |
| | 27 | |
| | 28 | == Proposal == |
| | 29 | |
| | 30 | Release strategy for stable release: |
| | 31 | * Stable releases are created on a time schedule: every six months |
| | 32 | * Stable releases are using even numbered branch created from trunk on code freeze (version RC0) |
| | 33 | * Release Candidate 1 is built two weeks after RC0 |
| | 34 | * Release Candidate 2 is built two weeks after RC1 |
| | 35 | * Final Release is built two weeks after RC2 |
| | 36 | * Stable releases are published in the main "!GeoNetwork_opensource" folder in sourceforge |
| | 37 | * Stable releases are annouced on user and devel mailing lists |
| | 38 | |
| | 39 | The Project Steering Committee (PSC) can postpone a stable release by vote on the mailing list. |
| | 40 | |
| | 41 | Between two stable releases, one or more alpha releases could be created. Alpha releases can be unstable. |
| | 42 | |
| | 43 | Release strategy for alpha release: |
| | 44 | * Alpha releases are created after major proposals have been added to trunk (feature based strategy) |
| | 45 | * Alpha releases are based on trunk and are built with uneven version numbers |
| | 46 | * Alpha releases are published in the "Unstable_GeoNetwork_opensource" folder |
| | 47 | * Alpha releases are annouced on devel mailing lists only |
| | 48 | |
| | 49 | Fixes are committed to both trunk and even numbered branch |
| | 50 | |
| | 51 | For releasing files on sourceforge.net : |
| | 52 | * follow [http://apps.sourceforge.net/trac/sourceforge/wiki/Release%20files%20for%20download these instructions] (release manager only) |
| | 53 | |
