It does - but it's useful only to developers and CM guys as a means to get
diffs to merge with your release candidates. The number itself has no
meaning whatsoever except to some revision previous to it - the changes
added as part of that revision are what you want, not the number itself.
Look at it this way - never tell your product manager or any other
non-programmer that revision number - tell them the bugs you fixed, and
you use those revision numbers to figure out which revision or collection
of revisions fixed which bugs.
I recommend a good issue tracking tool like Trac or Jira to help you
collect those revisions at a defect level, so that you'll know exactly
which diffs you need to merge with your release candidate.
If a defect shows that defect SUBVERSION-3343 is associated (in your issue
tracker) with revisions 33, 56, and 756, then you know that to fix that
defect in your release candidate, you must apply the differences between:
diff revision 32 and 33;
diff revision 55 and 56;
diff revision 755 and 756
and then you merge those diffs into your RC.
Now, revision 31 and 34 may be changes to something totally else (new
development not scheduled for this release, or maybe a bad checkin) so
what people are saying here is that they have no relevance to what you're
working on (Possibly) to your release, and that they are therefore not any
indication of what your release will contain.
If I made a cutoff date for code submission on Tuesday, and someone
checked in code on Wednesday and increased my revision number, I sure
don't want that code in my release, and therefore that revision number can
not have any significance to the current release.
and if I'm wrong on anything here, could Subversion guys who know better
please correct me!
-----Original Message-----
From: Rule, Chris [mailto:Chris.Rule@tbe.com]
Sent: Friday, June 17, 2005 12:53 PM
To: Ben Collins-Sussman; Ed Wittmann
Cc: users@subversion.tigris.org
Subject: RE: Re: Unclear: CVS and Subversion repository difference.
> -----Original Message-----
> From: Ben Collins-Sussman [mailto:sussman@collab.net]
> Sent: Friday, June 17, 2005 10:54 AM
> To: ed.wittmann@fiserv.com
> Cc: users@subversion.tigris.org
> Subject: Re: Unclear: CVS and Subversion repository difference.
>
> 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.
>
Hmmm. Revision numbers are reported under the "Known Bugs" section on the
subversion download site. So there is an interpretation used by the
subversion team that indicates maturity (assuming fixed bugs indicates
more mature). It also seems to be common to treat the revision number as a
build number again making it something more than just background noise.
It seems to me the revision number absolutly does indicate a version of a
project at a given point in time.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 17 19:24:34 2005