[ros-kernel] Release process

[Ge van Geldorp]

In general, I like the new release process with its branching, feature
freeze and code freeze. Some small points:

- It's not clear to me who's responsible for getting changes made in the
branch back into HEAD. In Vizinni's message "CVS Branching Proposal" of
2 Sept the proposal is: "Any commits on a branch must be merged into
HEAD by the committer". Then, Casper said on 5 Oct in a "Re: CVS Update:
reactos" message: "Don't fix it on both branches since CVS cannot track
what has been merged and what has not been merged". Either way works for
me, we just need to make a decision on it.

- Maybe we should put out a RC1 (Release Candidate) .iso at the
beginning of the feature freeze and a RC2 at the beginning of the code
freeze. Testers are not always developers and may have problems
building. Maybe by providing the .iso's more people would be willing to
test. More testers are needed in the future as we are moving slowly to
supporting third-party drivers.

- I would like to see a small change in the version numbering. At the
moment we have e.g. 0.1.4.3, with the ".3" meaning it was build on the
3rd day after the 0.1.4 release. I think this is a bit meaningless and
would like to propose 0.1.5-CVS for any past-0.1.4 build from HEAD,
0.1.5-RC1/0.1.5-RC2 for the next Release Candidates and plain 0.1.5 for
the next final release. Some changes will have to be made to our build
system for this, I volunteer to do that if this proposal is accepted.

Gé van Geldorp.