[Typo3-dev] RC2 out later today

[Peter Niederlag]

Hi Kasper,

Kasper Skårhøj schrieb am 26.04.2004 um 13:16 Uhr CEST

> 
> > 
> > (I am totally confused now anyway. ;) how can there be a
> > RC2_backupXXXX if there has not been a RC2 in first place?)
> 
> This is how I see the future:
> 
> Release: 3.6.0
> 
> In CVS:  3.6.1dev
> Release: 3.6.1
> 
> In CVS:  3.6.2dev
> Release: 3.6.2
> 
> In CVS:	 3.7.0RC1
> backups: ...3.7.0RC1_backup[date].tgz
> Release: 3.7.0RC1
> 
> It is based on the assumption that if "dev", "a", "b" or "rc" is
> appended to the version number it indicates a step *before* the final
> version.
> 
> How should the versioning policy be different? What should any
> intermediate version (in CVS / nightly backups) be if not the number
> to be released next?

how about '3.7-branch_backup' or '3.7_snapshot'?

As far as I understand it is best practice to have a Tag RC1 or
something to make a single distinguishable point in the source-code that
can be reverted to at any time. So there probably wouldn't be sense in a
_backup of a RC1. There should only be one RC1.tgz which should stay
just the same for all times.

I guess it would probably make sense to have RC1, RC2 etc _Tags_ in CVS
and _branches_ for 3.6, 3.7 etc. while we could easily make a tgz of the
tagged RC's and always have a recent snapshot of the branch available.

At least that's what seems to be clear to me still not being that
familiar with cvs branching/tagging. I am not sure how it could go with
the "policy" that currently rather uses personal branching than
functional/release branching.

Cheers,
PeterN
-- 
Peter Niederlag
http://www.niekom.de * Typo3 und EDV-Dienstleistungen *
http://www.clown-goli.de * Clown-Comedy-Jonglage-Animation *