| 1 | |
|---|
| 2 | HOWTO release ARB |
|---|
| 3 | ================= |
|---|
| 4 | |
|---|
| 5 | Overview: |
|---|
| 6 | |
|---|
| 7 | 1. 'trunk' versioning |
|---|
| 8 | 2. Create initial release candidate (rc1) |
|---|
| 9 | 3. Create subsequent release candidates (rc2,..) |
|---|
| 10 | 4. Create release |
|---|
| 11 | 5. Hotfixes for release |
|---|
| 12 | |
|---|
| 13 | -------------------------------------------------------------------------------- |
|---|
| 14 | |
|---|
| 15 | 1. 'trunk' versioning |
|---|
| 16 | |
|---|
| 17 | To check trunk version look into ../version_info |
|---|
| 18 | or call |
|---|
| 19 | make show_version |
|---|
| 20 | |
|---|
| 21 | 'trunk' shall always contain the release version number planned for the NEXT release. |
|---|
| 22 | |
|---|
| 23 | Example1: |
|---|
| 24 | last release was arb-5.5 |
|---|
| 25 | trunk should already contain arb-5.6 (or arb-6.0, whatever is planned) |
|---|
| 26 | |
|---|
| 27 | Example2: |
|---|
| 28 | last release was arb-5.5 |
|---|
| 29 | last rc was arb-6.0-rc1 |
|---|
| 30 | trunk should already contain arb-6.1 |
|---|
| 31 | |
|---|
| 32 | Intention is to have a explicit feature freeze whenever a rc is branched. |
|---|
| 33 | |
|---|
| 34 | To increment the version number, |
|---|
| 35 | - change into trunk WC |
|---|
| 36 | - svn update |
|---|
| 37 | - make inc_minor or inc_major |
|---|
| 38 | - in ../../arb_CHANGES.txt |
|---|
| 39 | - add missing changes |
|---|
| 40 | - update version info |
|---|
| 41 | - commit changes |
|---|
| 42 | |
|---|
| 43 | |
|---|
| 44 | 2. Create initial release candidate (rc1) |
|---|
| 45 | |
|---|
| 46 | - change into trunk WC and update to revision wanted for rc |
|---|
| 47 | - make sure the version number in trunk is already correct (see 1.) |
|---|
| 48 | To show it call |
|---|
| 49 | make show_version |
|---|
| 50 | - make sure arb_CHANGES.txt is up-to-date (i.e. lists changes for version-to-release) |
|---|
| 51 | - to make sure you are at HEAD call |
|---|
| 52 | svn update |
|---|
| 53 | - to branch the rc1 call |
|---|
| 54 | SOURCE_TOOLS/release/release_tool.pl branch_rc1 |
|---|
| 55 | |
|---|
| 56 | |
|---|
| 57 | 3. Create subsequent release candidates (rc2,..) |
|---|
| 58 | |
|---|
| 59 | Note: Subsequent release candidates are meant for bugfixes only! |
|---|
| 60 | |
|---|
| 61 | - change into 'rc' WC |
|---|
| 62 | - to increment rc number call |
|---|
| 63 | make inc_candi |
|---|
| 64 | - merge all bugfixes from trunk (or apply them in branch 'rc' and merge them back to trunk) |
|---|
| 65 | - commit changes and let a jenkins build pass (job 'ARB-rc'; builds automatically) |
|---|
| 66 | - to make sure you are at HEAD call |
|---|
| 67 | svn update |
|---|
| 68 | - call |
|---|
| 69 | SOURCE_TOOLS/release/release_tool.pl tag_rc |
|---|
| 70 | |
|---|
| 71 | |
|---|
| 72 | 4. Create release |
|---|
| 73 | |
|---|
| 74 | Note: Release should be a copy at the latest rc |
|---|
| 75 | |
|---|
| 76 | - change into 'rc' WC |
|---|
| 77 | - to make sure you are at HEAD call |
|---|
| 78 | svn update |
|---|
| 79 | - to branch the release call |
|---|
| 80 | SOURCE_TOOLS/release/release_tool.pl branch_stable |
|---|
| 81 | |
|---|
| 82 | Note: After the release is done, consider |
|---|
| 83 | - deleting the branch 'rc' or |
|---|
| 84 | - instantly create rc1 for next release (see 2. above). |
|---|
| 85 | |
|---|
| 86 | |
|---|
| 87 | 5. Hotfixes for release |
|---|
| 88 | |
|---|
| 89 | - change into 'stable' WC |
|---|
| 90 | - to increment the release patchlevel call |
|---|
| 91 | make inc_patch |
|---|
| 92 | - merge all hotfixes from trunk (or apply them in branch 'stable' and merge them back to trunk) |
|---|
| 93 | - commit changes and let a jenkins build pass (job 'ARB-stable'; builds automatically) |
|---|
| 94 | - to make sure you are at HEAD call |
|---|
| 95 | svn update |
|---|
| 96 | - call |
|---|
| 97 | SOURCE_TOOLS/release/release_tool.pl tag_stable |
|---|
