On Jun 17, 2005, at 10:29 AM, ed.wittmann@fiserv.com wrote:
>
> So I got them to talk about Release numbers in terms of phase and
> number
> (2.17, phase 2, release 17) and to let me worry about the revision
> numbers, and now everyone's happy. All I use the revision numbers
> for now
> is to determine what diffs to merge into my release candidate
> branches,
> and I gather those based on our issue tracking tool. When I'm done
> gathering those diffs into my release candidate branch, I tag and
> move on.
This is the key concept. A global repository revision has absolutely
nothing to do with the "version" of any project within the
repository. A project needs to invent its own release numbering
system and stick to it. A changing global repository revision is
just background noise, handles you can use to move around in time,
but totally unrelated to the software's maturity.
That's why svn, for example, has branches and tags named '1.1.x' and
'1.1.4'. *Those* are the only labels that matter.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 17 17:58:05 2005