[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Unclear: CVS and Subversion repository difference.

From: <ed.wittmann_at_fiserv.com>
Date: 2005-06-17 17:29:03 CEST

 I had a tough time getting our business analysts and project managers
weaned from the notion that revision numbers meant anything to them.
They'd be communicating to customers about deployment of build 10144 and
then some developer would find that he'd forgot to remove a
System.out.println and then we'd have a new revision number and that threw
all the managers and customers into a tizzy.

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.

-----Original Message-----
From: xevious@heavyphoton.com [mailto:xevious@heavyphoton.com]
Sent: Friday, June 17, 2005 11:16 AM
To: users@subversion.tigris.org
Subject: Re: Unclear: CVS and Subversion repository difference.

While impersonating an English Lit major, Servico Tpd Rodrigo Alfonso
Menezes Madera wrote:

> But does it make sense that yesterday you were working with

> revision 342 of Project2 and suddenly today in the morning > you are
working with revision 784? I mean, the guys from > Project45 have gone
wild in their nightly work, but why the > heck should that mess with me?
Project45 is a Web page, > they commit every second. And as an organized
person, > I preffer to know that my project increases itīs >
"not-to-be-considered" release as a helper, and not an > exposed
technical piece that we should share among all...

I also had more than a little pain getting my mind to accept the concept
behind this.

I think the point that may be somewhat hidden to you is that
Project2 is not at revision 784.

The *repository* is at revision 784. You may check out the latest version
of Project2 by checking out that folder in either revision 342 of the
repository or revision 784 of the repository. (Although, to reduce your
pain it would be better to check out the head revision - unless you need a
specific historical revision).

So, what is the version of your Project2? Whatever you want it to be -
preferably through a copy to the tags folder:

   Project2-AlmostWorks
   Project2-V1.08
   Project2-V1.09-Toxic
   Project2-V1.45-RC1

Etc. Obviously there is little point in tagging every commit. If you are
overly concerned - having observed an unexpected repository revision jump
- a *log* or *blame* will quickly tell you what is going on.

Having said all that, I often set up separate repositorys for separate
projects when they are wildly unrelated - primarily for ease of backups
and security maintenance. (Hello Enron? Thank you *so* much for SarbOx...)

xev

---------------------------------------------------------------------
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 17:30:56 2005

This is an archived mail posted to the Subversion Users mailing list.