> -----Ursprüngliche Nachricht-----
> Von: Thomas Beale [mailto:Thomas.Beale@OceanInformatics.biz]
> Gesendet: Dienstag, 2. August 2005 11:56
> An: Scott Palmer
> Cc: Subversion List
> Betreff: Re: early reflections on subversion methodology
>
> 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
>
>
I don't know how Scott handles his tags, but what we do is a directory structure such as:
[hope my ascii-art does not break]
repo_root ----
|
|--- project1
| |------ trunk
| |------ tags
| |------ branches
|
|--- project2
| |------ trunk
| |------ tags
| |------ branches
|
which makes tags and branches for each and every project live happily together, even if they carry the same name. The thing I like about it that it enables you to things like
repo_root ----
|
|--- project1
| |------ subproject1 (libs)
| | |------ trunk
| | |------ tags
| | |------ branches
| |
| |------ subproject2 (app)
| |------ trunk
| |------ tags
| |------ branches
|
|--- project2
| |------ trunk
| |------ tags
| |------ branches
|
which very nicely shows which projects are closely related but may still be used independ of others.
regards
fg
--
Felix Gilcher
Head of IT Development
Exozet Berlin GmbH
Rotherstraße 20
10245 Berlin
eMail: gilcher@exozet.com
URL: www.exozet.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 2 12:21:51 2005