1/ Release Cycle Announce | |
Public announce that The release is now started and can take some days. CVS is under pressure.
|
2/ Release Candidate branching | |
A branch in CVS is constituted for the release candidate, so if a developer want to add new features for the 1.7.1 or the 1.8 he can stick on the main trunk. But all avalaible efforts are required for bugfix, when possible.
|
3/ Release candidate diffusion | |
Extraction from CVS of a package from RC branch, as if it was the release, and public diffusion.
|
4/ Release Candidate testing and fixing (including finishing translations) | |
Directly on the CVS main trunk, all bugfixes are applied on the RC branch (that will be merged to main trunk at release time). Go to 3/ until no bugs (ideally) or just a few (if times passes too long).
|
5/ Evidence of the validity of a Release Candidate | |
When on the devel mailing-list there are enough of positive report about the stability of the release candidate, then Release is planned. It's an arbitrary decision that has to take in account that it's not good to stay in rc state too long, because merge bring more oddities when the branch separates too much from the trunk. Well, it's just comfort. If there is bugs, it's not releasable, that's what counts.
|
6/ Release Packaging | |
Tag of the final release_eta_carinea, then same steps as 4/ but, with release tag. Note that we will use a decompressed name of directory like tikiwiki_1.7 so we are compatible with gentoo update system (Lorinc plan).
|
7/ merging and branching | |
The branch release_eta_carinea should stay branched, as it will become the bugfix branch for an eventual 1.7.1 if it's required by circumstance (depends on number and severity level of bugs). The main trunk will be the 1.8 version, as we had recently a lot of new developers and they are planning to change (and ameliorate) many things. There will be probably another branching about an experimental database restructuration branch, because some homogeneity can be added, and it's a huge change. The 1.7 version is intended to be as stable as possible. all subsequent 1.7.x version will only be bugfixes, no added features. (hrum, I state that rather radically, please moderate me if I mistake).
|
8/ Public announce and release | |
That part is mostly under the coordination of marclaporte (to be written)
Further information
|