On 9/23/06, Erik Johansson <[EMAIL PROTECTED]> wrote:
The "old linux kernel versioning" scheme:
- Make the version in svn 1.3.3
- Release some (hopefully not that many) release candidates.
- When we are ready for a release, bump the version to 1.3.4, tag it in svn,
make the tarball and then update the version in trunk to 1.3.5.
- Develop new features/fix old bugs.
- Back to "Release some RCs"
The "it's version A until B is ready" scheme:
- Make the version in svn 1.3.2
- Release some more RCs
- When the release is ready, bump the version to 1.3.3, tag it in svn and make
the tarball (for this release this would have to be 1.3.4 since 1.3.4-rc1 is
already out, but in theory it would be 1.3.3).
- Develop some more.
- Release some RCs
- Make the 1.3.4 release, and so on
Currently I guess we use some kind of combination where the second scheme is
used, but at each version bump a version is skipped.
Historically, I was doing the old linux kernel scheme, but I didn't
know the linux kernel used to do it ;)
But out of pure laziness (and seeing no benefit of having odd-numbered
devel versions), I slipped into the latter scheme. So, from 1.3.4 we
will be using the second scheme and final releases can now be
odd-numbered.
Jon
--
________________________________________________________
Jon Keating ICQ: 16325723
[EMAIL PROTECTED] MSN: [EMAIL PROTECTED]
http://www.licq.org GPG: 2290A71F
http://www.thejon.org HOME: Minamiashigara, Japan
