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

Re: early reflections on subversion methodology

From: Thomas Beale <Thomas.Beale_at_OceanInformatics.biz>
Date: 2005-08-02 11:55:51 CEST

Scott Palmer wrote:

> On 1-Aug-05, at 5:41 AM, Thomas Beale wrote:
>> I haven't had the time to think an architectural solution through,
>> but all this sounds very reasonable. One thing I am fairly sure of:
>> there would not be any "tags" directory; I would simply record the
>> tag against the revision number being tagged. Of course this
>> mitigates against using multiple project trees in one repository,
>> which I initially thought sounded good, but in the end I think is
>> unusable; it has to be one project per repository. Doing otherwise
>> renders the versioning across the board completely meaningless, and
>> means that svn really is just a versioned file-system (and I'm not
>> knocking that!).
> I don't follow. I am currently using subversion with multiple
> projects per repository and I am recording milestones by revision
> number, not 'tags'. It works fine.

Are you saying that you don't use tags at all? What if you want to do a
checkout of a named revision, e.g. "release-0.9"? And normally, one
would want tags to apply on a per-project basis; e.g. "release-0.9" of
one project might co-exist with "alpha-release" and "dotnet-test" in
other projects. So you can't sensibly tag the entire repository with a
particular tag name; you have to copy prject subtrees into named tag
directories, which I would say is very prone to human error (even though
it probably is not in itself incorrect)...From what you say, you must be
managing a separate file of tags and revisions.

- thomas beale

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 2 11:59:36 2005

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.