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

svn vs cvs and version numbers

From: Tracy R Reed <treed_at_ultraviolet.org>
Date: 2007-07-03 19:25:22 CEST

My company is looking into converting our cvs repository to subversion.
However, our senior developer has a concern and I'm not quite sure how
to address the issue aside from "just use branches". Can anyone else
provide a more eloquent answer to this?

He says:

The problem with using SVN at our company derives from this feature: SVN
assigns a new version number to "the repository" for each "set" of
changes to the repository.

This differs from CVS. CVS assigns a new version number to "modifed each

Consider the following situation:

* We have a web site with two files: foo.php and bar.php.
* These two files have never been modified since they were initially
checked into the system.
* Fred makes copy edits to foo.php and commits the change.
* In CVS, foo.php has two versions: the version from the initial checkin
(1) and the modified version (2). bar.php has only the single version
representing its state when it was first checked in.
* In SVN, the repository has two versions: the state when foo.php and
bar.php were checked in (1) and the state after the changes to foo.php
were committed.
* Now Bob makes a copy edit to bar.php and commits the change.
* In CVS, foo.php and bar.php each have two versions.
* In SVN, there is now a third revision. The new revision (3)
represents the state of the repository after Dan committed his changes
to bar.php. This includes Fred's edits to bar.php.
* The client has sent the revisions of foo.php off to its lawyers for
review, and wants the changes to bar.php to be pushed live. The changes
to foo.php can't be pushed live until the lawyers approve the edit.
* In CVS, we can check out version 1 of foo.php and version 2 of bar.php
into a sandbox, tag it as RELEASE_TWO and move RELEASE_TWO into production.

In SVN, since the versioning happens on checkins and not on files, I
think we're screwed. I'd be happy for someone to straighten me out, though.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jul 3 19:25:27 2007

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.