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

RE: Symbolic Names

From: Tad Marko <tad.marko_at_bhnetwork.com>
Date: 2007-06-29 21:10:55 CEST

> Yes, when you see that happening, you can point people to this:
>
> http://subversion.tigris.org/mailing-list-guidelines.html#fresh-post

And I am already off and changing the subject. Let me come back to it.
I've been looking over subversion mailing list archives and I keep
finding lots of lively discussion about labels and symbolic names, often
times getting into the dev lists. I'm starting to assume that the
feature that I want is NOT yet implemented, so let me describe
specifically what I'm looking for and maybe it's just that I'm not
asking the right question.

I'd like the ability to drop some sort of a "semi" immutable breadcrumb
on a particular repository version. I say "semi-immutable" because I'd
like to be able to move the breadcrumb on purpose, but not accidentally.
I am very clear about the difference in SVN version numbers as compared
to CVS, which is obviously a side effect of the support for atomic
commits. I am fine associating a text breadcrumb with all files in a
repository.

I also understand that a tag = branch, or branch-tag in CVS parlance.
What I need is an analog to a CVS tag. I just want to be able to
associate human meaningful text with a particular repository version.
That text will then always relate to THAT version, unlike a SVN tag
which is a branch and will have its own mutable head.

My goal is to be able to notate a particular repository version with
something like "ReleaseCandidate", which will be moved occasionally, and
"Version 2.4", which will never move. This would be different than a
"Version 2.4" branch, which may or may not relate to the actual version
2.4 depending on if anyone has committed to that branch.

Yeah, there's a little bit of room for discussion about the discipline
of developers not committing to a branch vs. their discipline of not
relocating the semi-immutable breadcrumb. I perceive branches as easy to
change accidentally, these breadcrumbs as not as easy to change
accidentally.

Is there some way to do what I want here, is my thinking wrong, or is
there a more SVN-like way to do what I'm trying to accomplish? The
ultimate goal is for a large system, consisting of dozens of SVN
projects, to be easily kept organized by the build manager. This build
manager needs to be able to go to a particular project and know which
version the programmer wants him to promote to testing.

Thanks,
Tad

"Email Firewall" made the following annotations.
------------------------------------------------------------------------------

Warning:
All e-mail sent to this address will be received by the corporate e-mail system, and is subject to archival and review by someone other than the recipient. This e-mail may contain proprietary information and is intended only for the use of the intended recipient(s). If the reader of this message is not the intended recipient(s), you are notified that you have received this message in error and that any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately.
 
==============================================================================

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 29 21:11:16 2007

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