You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Tony Harverson <to...@iglu.com> on 2006/11/21 13:13:32 UTC
Simple Label=RevisionID Discussion
> -----Original Message-----
> From: Robert Graf-Waczenski [mailto:rgw@lsoft.com]
>
> Don't throw the word "branch" into this discussion! The issue
> at hand evolves around SVN's notion of "tagging" compared
> with various levels of a yet-to-be-defined support for
> labels, revision aliases, revision indexes or whatver else
> they have been called.
You're right, I meant "Tag" instead of "Branch". The Comment should have read:
"Yup, but that would be a tag, which is contended to be too
complex/complicated for non technical users or some of the projects
under discussion here. This discussion has the precept
that users do not want to copy off to another folder location, but want
to replace that functionality with a labelling feature set which is easier to use."
> *don't* want to get rid of using branches! But still we would
> benefit from label support in SVN (in our case: from trivial
> repo-wide revision aliases, we don't need the more complex
> variants that others have described and which arguably
> overlap with what the SVN devs intended with the "tag" concept.)
We desperately need to sever the various discussions in here, because we're chasing our tails discussing blurry and moving targets. *Your* requirement is for a simple revision = label mapping. The comment I replied to was in reply to a discussion about complex tags/labels, which is a semi-separate discussion.
If the simplest concept of a label (revision ID = "Label") was implemented, it would be useful for (for example) tagging the stable and production versions of an ongoing project. It would not, however, be useful for labelling releases, which seems to be the other requirement which is being loaded onto it. ( For reasons already covered in this thread, there's nowhere to commit fixes to in the second case, and the requirement becomes for complex tags, which is another discussion.
T
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: AW: Re: Re: Simple Label=RevisionID Discussion
Posted by Adam Gibson <ag...@ptm.com>.
Felix Gilcher wrote:
> just to put one thing straight: I'm not the one who brought up the idea of "labels as revision alias". I'm not opposed per se, but I don't think I need it (and haven't seen a usecase for it so far). I'm just throwing in problems I see with the suggestions made.
>
My reason for wanting it. There have been times when I have needed to
remove something from the repo (sensitive info or on rare occasions
major accidents that increase the repo size more than I like). This
shifts revision numbers. This really messes things up when I sometimes
need to record the revisions numbers I merged some changes from in the
commit log. There are times when you only need parts of a branch
merged. If I could use a label name instead of a revision number it
would move to the new revision number automatically.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
AW: Re: Re: Simple Label=RevisionID Discussion
Posted by Felix Gilcher <gi...@exozet.com>.
just to put one thing straight: I'm not the one who brought up the idea of "labels as revision alias". I'm not opposed per se, but I don't think I need it (and haven't seen a usecase for it so far). I'm just throwing in problems I see with the suggestions made.
John Rouillard <ma...@renesys.com> schrieb am Mittwoch, 22. November 2006 18:08:
> On Wed, Nov 22, 2006 at 05:22:45PM +0100, Felix Gilcher wrote:
>> John Rouillard <ma...@renesys.com> schrieb am
> Mittwoch, 22. November 2006 16:53:
>>
>>> On Wed, Nov 22, 2006 at 09:49:01AM +0100, Robert
> Graf-Waczenski wrote:
>>>>> 2. How many labels can be attached to a revision? One? Any number?
>>>>
>>>> Only one. (Remember, we're talking *poor* man's labels here...)
>>>
>>> So adding a new label to the rev destroys the old label? I think
>>> this is wrong. Any given revision should be able to have the same
>>> label. Especially with mutable labels you may need to double label
>>> a revision with a permanent label (say PRODUCTION_2006_11_22) and a
>>> floating lable (CURRENT_PRODUCTION).
>>
>> I see you're trying to replace tags by labels. You really should be
>> aware that if a label is a revision alias it does not carry enough
>> information to identify a production release. Regard subversion as a
>> versioned filesystem. Every resource can be identified by 2
>> coordinates: a paths and a time coordinate.
>
> With you so far. I think I am the one who made the original argument
> on tags being really revisions and therefore are time based but that
> svn represents (confusingly) in path space.
>
IMHO, tags are no time alias. Tags are in themselves a combination of space and time (they can be traced back to a specific revision of a set of specific paths). This is why they need to be immutable. Their representation is secondary and I have no conceptual problem with placing them in the path space. It's just like I could do a photocopy of a letter I'm handwriting and put it in a folder on my shelf. It would be a "time snapshot" of a "3d Space Item" represented by a "3d Space Item" that is immutable over time.
>> Time is what you specify
>> with the revision argument to the svn command unless HEAD is
>> implied. So what does a label "PRODUCTION" mean if it references
>> revision X?
>
> "revision X" of a file. Not of the repository. I think this may have
> diverged a bit. Is your PMT a symbolic name for -r 121 of every file
> in the repository, or is it a symbolic name that can be applied to
> individual files/paths in the repository?
>
To quote the original poster: "A PML can be attached to any existing revision, similar to
revision properties." I'd read it as "label X maps to revision Y for the whole repository" - a mnemonic alias for a given repository revision number.
>> Is it
>>
>> componentY/stable/version1/ at revision X
>>
>> or maybe
>>
>> componentY/development/currently_broken/ at revision X
>
> It can be either same as a tag can represent either. It's just a name
> for a file at a particular version of the repository.
as quoted: It's a revision number - not a name for a file at a revision.
>
> Much the same as -r 121 can be broken for some path in the repository
> and working for some other path.
>
>> Things get even worse when you have a repository as the apache
>> foundation [1] has: all ASF projects from ANT to xmlgraphics are in
>> a single repository - this is quite a common usecase. What does the
>> label "PRODUCTION" mean in this context?
>
> What does any label mean then? If the label is repository revision
> wide, then ant at "Rel 1.0" of the repository may be totally broken
> since "Rel 1.0" was meant to be release 1.0 of xmlgraphics which does
> work.
>
>> So you'd have to specify
>>
>> svn co -r"APR_PRODUCTION"
> http://svn.apache.org/repos/asf/apr/apr/trunk/
>>
>> or something similar instead of
>>
>> svn co http://svn.apache.org/repos/asf/apr/apr/tags/1.2.7/
>>
>> Which one of the two is more error prone?
>
> Neither, either. Depends on what you are used to. I would think the
> first would map to most people's way of thinking better. I want these
> files at this time. Not those other files. I do agree that the tags
> being mapped to a pure URL is easier to transport and link to
> however, but we could also do:
>
> http://svn.apache.org/repos/asf/apr/apr/trunk/#APR_PRODUCTION
>
> and define that convention to get the same ease.
so you're mapping the whole time component back into path space for ease. Why that - you can have this right now.
>
>> Without a doubt the first
>> one. What happens if you confuse which labels belong to which path
>> of your project? You may get build errors or even worse build and
>> release old, buggy versions. The current tagging mechanism is way
>> more suited to identifying frozen revisions such as "PRODUCTION".
>
> What you are assuming is that there is a simple way to create the tag
> and in a mixed revision "releases" there may not be. If I have 100
> files from 10 different revisions I need an easy way to label those
> files at a given revision. Copying them all to path space in a working
> copy is a major pain. Labels (as I think you said) can be applied to
> any revision anywhere in the path space.
>
So what you need might be just a convinient UI to do this:
svn copy -r X proto://repo/trunk/path/to/file1 proto://repo/tags/mytag/path/to/file1
svn copy -r Y proto://repo/trunk/path/to/file2 proto://repo/tags/mytag/path/to/file2
svn copy -r X proto://repo/trunk/path/to/folder1 proto://repo/tags/mytag/path/to/folder1
There is no enforced requirement that a tag must be created in a single operation - it would be nice, but it doesn't have to be this way. Important is that once created it's immutable.
I might be wrong here (it's a long time since I used CVS):
In CVS you'd have to tag each file manually as well unless you tag a working copy. How did you get your working copy in CVS in the first place? By pulling the proper revisions, same as now.
> I've been there, it's a major hassle that doesn't exist with CVS and
> the ability to retag (re-label) files.
>
> What I want is an easy way to stay inthe time dimention and group
> revisions in the time dimention.
>
> See the last graphic in:
>
> http://ximbiot.com/cvs/manual/cvs-1.11.22/cvs_4.html#SEC48
>
> I want that arrow linking the files. The only difference would be that
> the revision numbers are not per file but per repository. So rather
> than 1.2 think 12.
If you have a tag you can pull all those files. Just specify the tag as source.
>
> I could use branches/tags but the major overhead of switching,
> updating and trying to keeping them up to date is a nightmare. Plus I
> lose the history info for the file that has occurred since the
> branch. I get the prior info but if I want to see what has changed in
> themainline version of the file, I cn't do that by looking at the
> branch. I have to manually:
>
> identify the trunk revision where the tagged copy came off the
> trunk
>
> locate the trunk copy's path and svn log it.
>
> I can't just svn log the trunk copy and scan back to the location
> where the label was set, or even:
>
> svn log -r LABEL:HEAD trunk/file
That's what I'm trying to point at: Why not create a wrapper-script for svn that allows this syntax:
svn log -r"path/to/tag/one:HEAD" trunk/file
The wrapper looks up the url, parses the log, calls the "real" svn with the proper arguments and you're done. No need for a secondary mechanism, everything solved with existant tools.
>
> so the log info stops at the LABEL (I think I got the syntax right
> but I hope you get the idea).
>
I agree with you that the current workflow is akward sometimes, but noone forces you to do everything manually. I don't agree with the notion that labels are the magic silver bullet solving this problem.
> Now I ask you which is more error prone?
Everything by hand. But as above: Your computer is expert at solving stupid repetitive tasks. Make him your slave and helper.
>
> Basically copying the file breaks the timeline in major ways and I am
> trying to get some way of maintaining the timeline and being able to
> identify particular revisions of files that can be checked
> out/diffed/updated to etc. as a unit.
Tortoise allows you to build a revision graph. The information is available, it just that noone built a utility to display it. Retrieving this information is a bit slow at the moment, however solving this is a completely different problem and I don't think that anyone would be opposed to a good solution.
>
>> Make it possible to specify a svn url in the -r argument. If the
>> argument is an url, it gets replaced by the revision in which the
>> branch/tag was created. There are some corner cases (what happens if
>> the url does not point to branch etc.), but it would be possible to
>> create such an implementation as a shellwrapper to svn for testing
>> purposes.
>
> That doesn't address the difficulty in creating the tag in the first
> place.
How about trying to build a more convinient tool that does this for you? Maybe a script that accepts multiple files as input and calls the proper commands in the background? something like:
svntag path/to/file/one#rev1 path/to/file/2#rev3 /path/to/folder/one#HEAD /path/to/tag/mytag
regards
felix
--
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
Re: Re: Simple Label=RevisionID Discussion
Posted by John Rouillard <ro...@renesys.com>.
On Wed, Nov 22, 2006 at 05:22:45PM +0100, Felix Gilcher wrote:
> John Rouillard <ma...@renesys.com> schrieb am Mittwoch, 22. November 2006 16:53:
>
> > On Wed, Nov 22, 2006 at 09:49:01AM +0100, Robert Graf-Waczenski wrote:
> >>> 2. How many labels can be attached to a revision? One? Any number?
> >>
> >> Only one. (Remember, we're talking *poor* man's labels here...)
> >
> > So adding a new label to the rev destroys the old label? I think this
> > is wrong. Any given revision should be able to have the same label.
> > Especially with mutable labels you may need to double label a revision
> > with a permanent label (say PRODUCTION_2006_11_22) and a floating
> > lable (CURRENT_PRODUCTION).
>
> I see you're trying to replace tags by labels. You really should be
> aware that if a label is a revision alias it does not carry enough
> information to identify a production release. Regard subversion as a
> versioned filesystem. Every resource can be identified by 2
> coordinates: a paths and a time coordinate.
With you so far. I think I am the one who made the original argument
on tags being really revisions and therefore are time based but that
svn represents (confusingly) in path space.
> Time is what you specify
> with the revision argument to the svn command unless HEAD is
> implied. So what does a label "PRODUCTION" mean if it references
> revision X?
"revision X" of a file. Not of the repository. I think this may have
diverged a bit. Is your PMT a symbolic name for -r 121 of every file
in the repository, or is it a symbolic name that can be applied to
individual files/paths in the repository?
>Is it
>
> componentY/stable/version1/ at revision X
>
> or maybe
>
> componentY/development/currently_broken/ at revision X
It can be either same as a tag can represent either. It's just a name
for a file at a particular version of the repository.
Much the same as -r 121 can be broken for some path in the repository
and working for some other path.
> Things get even worse when you have a repository as the apache
> foundation [1] has: all ASF projects from ANT to xmlgraphics are in
> a single repository - this is quite a common usecase. What does the
> label "PRODUCTION" mean in this context?
What does any label mean then? If the label is repository revision
wide, then ant at "Rel 1.0" of the repository may be totally broken
since "Rel 1.0" was meant to be release 1.0 of xmlgraphics which does
work.
> So you'd have to specify
>
> svn co -r"APR_PRODUCTION" http://svn.apache.org/repos/asf/apr/apr/trunk/
>
> or something similar instead of
>
> svn co http://svn.apache.org/repos/asf/apr/apr/tags/1.2.7/
>
> Which one of the two is more error prone?
Neither, either. Depends on what you are used to. I would think the
first would map to most people's way of thinking better. I want these
files at this time. Not those other files. I do agree that the tags
being mapped to a pure URL is easier to transport and link to however,
but we could also do:
http://svn.apache.org/repos/asf/apr/apr/trunk/#APR_PRODUCTION
and define that convention to get the same ease.
> Without a doubt the first
> one. What happens if you confuse which labels belong to which path
> of your project? You may get build errors or even worse build and
> release old, buggy versions. The current tagging mechanism is way
> more suited to identifying frozen revisions such as "PRODUCTION".
What you are assuming is that there is a simple way to create the tag
and in a mixed revision "releases" there may not be. If I have 100
files from 10 different revisions I need an easy way to label those
files at a given revision. Copying them all to path space in a working
copy is a major pain. Labels (as I think you said) can be applied to
any revision anywhere in the path space.
I've been there, it's a major hassle that doesn't exist with CVS and
the ability to retag (re-label) files.
What I want is an easy way to stay inthe time dimention and group
revisions in the time dimention.
See the last graphic in:
http://ximbiot.com/cvs/manual/cvs-1.11.22/cvs_4.html#SEC48
I want that arrow linking the files. The only difference would be that
the revision numbers are not per file but per repository. So rather
than 1.2 think 12.
I could use branches/tags but the major overhead of switching,
updating and trying to keeping them up to date is a nightmare. Plus I
lose the history info for the file that has occurred since the
branch. I get the prior info but if I want to see what has changed in
themainline version of the file, I cn't do that by looking at the
branch. I have to manually:
identify the trunk revision where the tagged copy came off the
trunk
locate the trunk copy's path and svn log it.
I can't just svn log the trunk copy and scan back to the location
where the label was set, or even:
svn log -r LABEL:HEAD trunk/file
so the log info stops at the LABEL (I think I got the syntax right but
I hope you get the idea).
Now I ask you which is more error prone?
Basically copying the file breaks the timeline in major ways and I am
trying to get some way of maintaining the timeline and being able to
identify particular revisions of files that can be checked
out/diffed/updated to etc. as a unit.
> Make it possible to specify a svn url in the -r argument. If the
> argument is an url, it gets replaced by the revision in which the
> branch/tag was created. There are some corner cases (what happens if
> the url does not point to branch etc.), but it would be possible to
> create such an implementation as a shellwrapper to svn for testing
> purposes.
That doesn't address the difficulty in creating the tag in the first
place.
--
-- rouilj
John Rouillard
System Administrator
Renesys Corporation
603-643-9300 x 111
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: AW: Re: Simple Label=RevisionID Discussion
Posted by Robert Graf-Waczenski <rg...@lsoft.com>.
> I think these three issues wil have to be dealt with *in the proposal*
> if the ultimate goal is to write a proposal that would convince the
> existing Subversion developers.
>
> With regards,
> Gerco (only trying to be constructive).
Succeeded. (At least for me..)
> > On Nov 23, 2006, at 5:18 AM, Gerco Ballintijn wrote:
> >
> >> Tim Hill wrote:
> >>> I cannot talk for others, but my intention has _never_ been to
> >>> replace tags with labels, for the very reasons you state. However,
> >>> you are talking about _your_ usage model for subversion. There are
> >>> many, many installs where Subversion is used as little more than a
> >>> historical time-machine for a simple, linear, development cycle. In
> >>> these simple scenarios there is _NO_ "path" co-ordinate to manage,
> >>> since there are no branches at all: everything happens on the trunk
> >>> (yes, really!).
> >>
> >> I assume you also "require" that only a single "project" is maintained
> >> per repository.
> >>
> >> The workflow context of your proposol would thus be:
> >> - Single project per repository
> >> - No branches
> >> - No tags
I don't see why you think that the workflow context would be such that
the intended user type would not use branching. Yes, Tim describes a
scenario were everything happens on the trunk. Clearly for such a scenario
the proposed PML would be a fine mechanism re-create older builds
by referring to old rev#s with a revision alias.
But also a project such as the one i'm working in since several
years would benefit from PMLs because this would free us from the
need to create tags. We *need* branches simply because we have
several releases to maintain in parallel, so there definitely is a
space co-ordinate to manage. We would like to use SVN without tags
but instead with PMLs that point to the correct time co-ordinate.
And, to us, this time co-ordinate is meaningfull in all branches.
My goal with this proposal is to make the implementation close to
trivial and the benefit as high as possible, so any comment is welcome
that refines the proposal in such a way that the developers feel good
about adding it and also don't see too much side effects in the
implementation.
Robert
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: AW: Re: Simple Label=RevisionID Discussion
Posted by Gerco Ballintijn <ge...@ballintijn.com>.
Yes, you have. Perhaps I should have been more clear.
The *summary* in the first part of my email was intended to make the
point that it would be useful to add these restrictions to the proposal
since it further defines the intended scope of the solution, thereby
avoiding feature drift.
The second point I tried to make was that there is the suggestion of
two discrete groups of people: simple users that would use labels and
advanced users that would use tags. That seems to be a significant
simplification of the world at large. Furthermore upgrade issues will
exist.
I think these three issues wil have to be dealt with *in the proposal*
if the ultimate goal is to write a proposal that would convince the
existing Subversion developers.
With regards,
Gerco (only trying to be constructive).
Tim Hill wrote:
> Frankly, I've discussed these issues in an earlier post, where I made
> clear my opinions on pretty much all of this.
>
> --Tim
>
> On Nov 23, 2006, at 5:18 AM, Gerco Ballintijn wrote:
>
>> Tim Hill wrote:
>>> I cannot talk for others, but my intention has _never_ been to
>>> replace tags with labels, for the very reasons you state. However,
>>> you are talking about _your_ usage model for subversion. There are
>>> many, many installs where Subversion is used as little more than a
>>> historical time-machine for a simple, linear, development cycle. In
>>> these simple scenarios there is _NO_ "path" co-ordinate to manage,
>>> since there are no branches at all: everything happens on the trunk
>>> (yes, really!).
>>
>> I assume you also "require" that only a single "project" is maintained
>> per repository.
>>
>> The workflow context of your proposol would thus be:
>> - Single project per repository
>> - No branches
>> - No tags
>>
>> This means that your "simple" users should be kept away from Subversion
>> documents that describe these techniques. I am not so sure that you can
>> contain your (and not just your) users in this simplified Subversion
>> world.
>>
>> Have you considered the "upgrade" problems? People that think they can
>> suffice with labels, but at a later require more functionality and
>> need the current tagging mechanism. For instance, because they want to
>> add an extra project to the repository, and thus have projects that
>> share the same label name space? I expect this to an extra source of
>> confusion.
>>
>> As a side note, it is a "policy break" in Subversion that two over-
>> lapping concepts (in this case actually one a subset of the other), get
>> different mechanism to satisfy different user groups. I can imagine that
>> the Subversion stewards would find this a dangerous precedent (the
>> slippery slope argument).
>>
>> With regards,
>> Gerco.
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: AW: Re: Simple Label=RevisionID Discussion
Posted by Tim Hill <dr...@comcast.net>.
Frankly, I've discussed these issues in an earlier post, where I made
clear my opinions on pretty much all of this.
--Tim
On Nov 23, 2006, at 5:18 AM, Gerco Ballintijn wrote:
> Tim Hill wrote:
>> I cannot talk for others, but my intention has _never_ been to
>> replace tags with labels, for the very reasons you state. However,
>> you are talking about _your_ usage model for subversion. There are
>> many, many installs where Subversion is used as little more than a
>> historical time-machine for a simple, linear, development cycle.
>> In these simple scenarios there is _NO_ "path" co-ordinate to
>> manage, since there are no branches at all: everything happens on
>> the trunk (yes, really!).
>
> I assume you also "require" that only a single "project" is maintained
> per repository.
>
> The workflow context of your proposol would thus be:
> - Single project per repository
> - No branches
> - No tags
>
> This means that your "simple" users should be kept away from
> Subversion
> documents that describe these techniques. I am not so sure that you
> can
> contain your (and not just your) users in this simplified Subversion
> world.
>
> Have you considered the "upgrade" problems? People that think they can
> suffice with labels, but at a later require more functionality and
> need the current tagging mechanism. For instance, because they want
> to add an
> extra project to the repository, and thus have projects that share the
> same label name space? I expect this to an extra source of confusion.
>
> As a side note, it is a "policy break" in Subversion that two over-
> lapping concepts (in this case actually one a subset of the other),
> get
> different mechanism to satisfy different user groups. I can imagine
> that
> the Subversion stewards would find this a dangerous precedent (the
> slippery slope argument).
>
> With regards,
> Gerco.
>
> ---------------------------------------------------------------------
> 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
Re: AW: Re: Simple Label=RevisionID Discussion
Posted by Tim Hill <dr...@comcast.net>.
Indeed. And consider another real-world scenario (from personal
experience)...
I use a defect tracking tool that can track defects in many projects
at once. It uses a single defect ID "namespace" across all projects,
so the single defect ID not only identifies the defect but also the
project. In other works, it uses defect ID in the same way Subversion
uses rev numbers. Both very good, imho.
So, what about a workflow where I want to audit each commit with a
defect ID? How do I do this today? The official answer is with a bit
of syntactic sugar in the log message, something like "DEFECTID:
5673". If I had a label scheme I could simply enter a label with this
information.
Why is the label better? Because its more structured. Because its
easier/faster for tools to process than grepping all over log
messages. Because its orthogonal to the already badly overloaded log
message.
--Tim
On Nov 24, 2006, at 6:19 AM, Mark Clements wrote:
> "Gerco Ballintijn" <ge...@ballintijn.com> wrote in message
> news:45659FC1.7070002@ballintijn.com...
>> Tim Hill wrote:
>>>
>>> I cannot talk for others, but my intention has _never_ been to
>>> replace
>>> tags with labels, for the very reasons you state. However, you are
>>> talking about _your_ usage model for subversion. There are many,
>>> many
>>> installs where Subversion is used as little more than a historical
>>> time-machine for a simple, linear, development cycle. In these
>>> simple
>>> scenarios there is _NO_ "path" co-ordinate to manage, since there
>>> are no
>>> branches at all: everything happens on the trunk (yes, really!).
>>>
>>
>> I assume you also "require" that only a single "project" is
>> maintained
>> per repository.
>>
>
> Labels (as aliases for revision numbers) are still useful in complex
> repositories, even those containing multiple projects.
>
> I can imagine the following labels being pretty useful:
>
> "Repository restored after server crash - May 06"
> "James left the development team"
> "Switched to using svnserve."
> "Policy change: no commits without an associated bug number"
> etc.
>
> - Mark Clements (HappyDog)
>
>
>
> ---------------------------------------------------------------------
> 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
Re: AW: Re: Simple Label=RevisionID Discussion
Posted by Mark Clements <gm...@kennel17.co.uk>.
"Gerco Ballintijn" <ge...@ballintijn.com> wrote in message
news:45659FC1.7070002@ballintijn.com...
> Tim Hill wrote:
> >
> > I cannot talk for others, but my intention has _never_ been to replace
> > tags with labels, for the very reasons you state. However, you are
> > talking about _your_ usage model for subversion. There are many, many
> > installs where Subversion is used as little more than a historical
> > time-machine for a simple, linear, development cycle. In these simple
> > scenarios there is _NO_ "path" co-ordinate to manage, since there are no
> > branches at all: everything happens on the trunk (yes, really!).
> >
>
> I assume you also "require" that only a single "project" is maintained
> per repository.
>
Labels (as aliases for revision numbers) are still useful in complex
repositories, even those containing multiple projects.
I can imagine the following labels being pretty useful:
"Repository restored after server crash - May 06"
"James left the development team"
"Switched to using svnserve."
"Policy change: no commits without an associated bug number"
etc.
- Mark Clements (HappyDog)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: AW: Re: Simple Label=RevisionID Discussion
Posted by Gerco Ballintijn <ge...@ballintijn.com>.
Tim Hill wrote:
>
> I cannot talk for others, but my intention has _never_ been to replace
> tags with labels, for the very reasons you state. However, you are
> talking about _your_ usage model for subversion. There are many, many
> installs where Subversion is used as little more than a historical
> time-machine for a simple, linear, development cycle. In these simple
> scenarios there is _NO_ "path" co-ordinate to manage, since there are no
> branches at all: everything happens on the trunk (yes, really!).
>
I assume you also "require" that only a single "project" is maintained
per repository.
The workflow context of your proposol would thus be:
- Single project per repository
- No branches
- No tags
This means that your "simple" users should be kept away from Subversion
documents that describe these techniques. I am not so sure that you can
contain your (and not just your) users in this simplified Subversion
world.
Have you considered the "upgrade" problems? People that think they can
suffice with labels, but at a later require more functionality and need
the current tagging mechanism. For instance, because they want to add an
extra project to the repository, and thus have projects that share the
same label name space? I expect this to an extra source of confusion.
As a side note, it is a "policy break" in Subversion that two over-
lapping concepts (in this case actually one a subset of the other), get
different mechanism to satisfy different user groups. I can imagine that
the Subversion stewards would find this a dangerous precedent (the
slippery slope argument).
With regards,
Gerco.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: AW: Re: Simple Label=RevisionID Discussion
Posted by Brad Bruce <NJ...@Verizon.net>.
Tim Hill wrote:
> Felix,
>
> I cannot talk for others, but my intention has _never_ been to replace
> tags with labels, for the very reasons you state. However, you are
> talking about _your_ usage model for subversion. There are many, many
> installs where Subversion is used as little more than a historical
> time-machine for a simple, linear, development cycle. In these simple
> scenarios there is _NO_ "path" co-ordinate to manage, since there are
> no branches at all: everything happens on the trunk (yes, really!).
>
> This comes back to my basic argument: _Simple_ uses of subversion need
> a _simple_ way to symbolically track the timeline. Tags are not
> simple. Hence labels. Simple labels are not suitable for non-linear
> (read: anything except simple) dev cycles, and for that we have tags.
>
> --Tim
>
>
> On Nov 22, 2006, at 8:22 AM, Felix Gilcher wrote:
>
>> John Rouillard <ma...@renesys.com> schrieb am Mittwoch, 22.
>> November 2006 16:53:
>>
>>> On Wed, Nov 22, 2006 at 09:49:01AM +0100, Robert Graf-Waczenski wrote:
>>>>> 2. How many labels can be attached to a revision? One? Any number?
>>>>
>>>> Only one. (Remember, we're talking *poor* man's labels here...)
>>>
>>> So adding a new label to the rev destroys the old label? I think this
>>> is wrong. Any given revision should be able to have the same label.
>>> Especially with mutable labels you may need to double label a revision
>>> with a permanent label (say PRODUCTION_2006_11_22) and a floating
>>> lable (CURRENT_PRODUCTION).
>>
>> I see you're trying to replace tags by labels. You really should be
>> aware that if a label is a revision alias it does not carry enough
>> information to identify a production release. Regard subversion as a
>> versioned filesystem. Every resource can be identified by 2
>> coordinates: a paths and a time coordinate. Time is what you specify
>> with the revision argument to the svn command unless HEAD is implied.
>> So what does a label "PRODUCTION" mean if it references revision X?
>> Is it
>>
>> componentY/stable/version1/ at revision X
>>
>> or maybe
>>
>> componentY/development/currently_broken/ at revision X
>>
>> Things get even worse when you have a repository as the apache
>> foundation [1] has: all ASF projects from ANT to xmlgraphics are in a
>> single repository - this is quite a common usecase. What does the
>> label "PRODUCTION" mean in this context?
>>
>> So you'd have to specify
>>
>> svn co -r"APR_PRODUCTION" http://svn.apache.org/repos/asf/apr/apr/trunk/
>>
>> or something similar instead of
>>
>> svn co http://svn.apache.org/repos/asf/apr/apr/tags/1.2.7/
>>
>> Which one of the two is more error prone? Without a doubt the first
>> one. What happens if you confuse which labels belong to which path of
>> your project? You may get build errors or even worse build and
>> release old, buggy versions. The current tagging mechanism is way
>> more suited to identifying frozen revisions such as "PRODUCTION".
>>
>> So what I'm missing in this discussion is what exact benefits do you
>> all expect from labels as revision ids? What about this:
>>
>> Make it possible to specify a svn url in the -r argument. If the
>> argument is an url, it gets replaced by the revision in which the
>> branch/tag was created. There are some corner cases (what happens if
>> the url does not point to branch etc.), but it would be possible to
>> create such an implementation as a shellwrapper to svn for testing
>> purposes.
>>
>>
>> regards
>>
>> felix
>>
>>
>> [1] http://svn.apache.org/repos/asf/
>>
>> --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
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
At work we have a version control client that consolidates multiple
repositories into one interface.
In order to make it easier for some people to handle promotions, we
created a labeling system that was outside of the normal Subversion
system. It consists of a small SqLite database with a table holding
Repository Name, Label Name, Branch and revision.
The people who know Subversion create the shortcut entries, then
everyone else can use the shortcut entries to get to where they're going.
This works well when code is turned over for testing. The testers only
need to look up the project and the "Ready for Test" shortcut. The
system takes them to the correct branch and revision.
Brad Bruce
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: AW: AW: Re: Simple Label=RevisionID Discussion
Posted by Tim Hill <dr...@comcast.net>.
>>
>
> I hope you can see as clear as I do that people are trying to
> evolve your "PML" into a full blown secondary tagging mechanism.
> What I like about svn is that there is a simple way of doing
> things, creating a tag. It's really dead simple, I make a copy,
> just as I used to do back when noone was talking about revision
> control: place a backup somewhere. Creating a secondary tagging
> mechanism makes the whole thing go from sleek and efficient to
> bloated and overburdened. I agree that some workflows can be
> streamlined and that some paradigms are sometimes awkward for small
> scale projects but I really prefer it over ambigious behaviour and
> tons of options, multiple ways of doing things.
>
> I understand that your intention is to make things better and
> simpler, but often the worst things stem from purely good
> intentions. I'd rather prefer to map the simpler workflows we both
> want to the "regular" workflows and hide that fact from the user.
> The tortoiseSVN "tag" command is just this example. It does offer a
> nice interface to tagging and in the background creates a copy.
>
Yes, I do see this, and it's pretty normal for any new feature to
initially bloat as people try to bolt on all sorts of edge cases.
Myself I always apply the 80:20 rule (80% of use cases are satisfied
by 20% of the proposed features).
In fact, if you look carefully at my previous proposal, you'll notice
that, in fact, its just really a slightly disguised revision property
with some command-line sugar. I like this because (a) it gives people
labels, (b) it doesn't change the repository schema or protocol and
(c) its fully forward and backward compatible.
My thinking goes like this:
-- A "label" is a symbolic name for a revision. Therefore its a
property of a revision. Therefore its a revision property.
-- BUT revprops are, by default, disabled in Subversion, since they
can break old revisions by making retroactive state changes.
-- BUT a label (revprop) that is set _only_ at commit time (i.e. when
the rev is created) does NOT have this flaw.
-- Therefore, the need is for relaxing the revprop rules such that
they _can_ be set at commit time, but otherwise follow the same
restrictions as currently.
-- Therefore, Subversion needs the ability to set revprops atomically
at commit time.
So, we have something like this:
svn commit ... --revprop name "VALUE"
Which does a commit and includes the named revprop.
And I really think that's it! Yes, using labels in rev#s would be
nice, but not necessary.
--Tim
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
AW: AW: Re: Simple Label=RevisionID Discussion
Posted by Felix Gilcher <gi...@exozet.com>.
Tim Hill <ma...@comcast.net> schrieb am Mittwoch, 22. November 2006 18:37:
> Felix,
>
> I cannot talk for others, but my intention has _never_ been to
> replace tags with labels, for the very reasons you state.
I guessed that.
> However,
> you are talking about _your_ usage model for subversion.
Hey, The ASF repository is not *my* usage model, just a convienient example of an extreme case. However, this model does exist, is acknowledged as a possible solution and any label solution being discussed IMHO *must not* introduce any problems for those usage models.
> There are
> many, many installs where Subversion is used as little more than a
> historical time-machine for a simple, linear, development cycle. In
> these simple scenarios there is _NO_ "path" co-ordinate to manage,
> since there are no branches at all: everything happens on the trunk
> (yes, really!).
I know, I do have those projects as well (we're doing some quite simple websites sometimes and they don't need a complicated development workflow). However, tagging from the trunk works nicely for those once you get used to it (this is at least my experience). You're not likely to get a large number of revisions for those projects either, so you could get away with revision properties or placing a "stable_revisions.csv" somewhere in the root folder. Write a wrapper that handles the file or properties and you're done.
>
> This comes back to my basic argument: _Simple_ uses of subversion
> need a _simple_ way to symbolically track the timeline. Tags are not
> simple. Hence labels. Simple labels are not suitable for non-linear
> (read: anything except simple) dev cycles, and for that we have tags.
>
I hope you can see as clear as I do that people are trying to evolve your "PML" into a full blown secondary tagging mechanism. What I like about svn is that there is a simple way of doing things, creating a tag. It's really dead simple, I make a copy, just as I used to do back when noone was talking about revision control: place a backup somewhere. Creating a secondary tagging mechanism makes the whole thing go from sleek and efficient to bloated and overburdened. I agree that some workflows can be streamlined and that some paradigms are sometimes awkward for small scale projects but I really prefer it over ambigious behaviour and tons of options, multiple ways of doing things.
I understand that your intention is to make things better and simpler, but often the worst things stem from purely good intentions. I'd rather prefer to map the simpler workflows we both want to the "regular" workflows and hide that fact from the user. The tortoiseSVN "tag" command is just this example. It does offer a nice interface to tagging and in the background creates a copy.
> --Tim
>
>
regards
felix
--
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
Re: AW: Re: Simple Label=RevisionID Discussion
Posted by Tim Hill <dr...@comcast.net>.
Felix,
I cannot talk for others, but my intention has _never_ been to
replace tags with labels, for the very reasons you state. However,
you are talking about _your_ usage model for subversion. There are
many, many installs where Subversion is used as little more than a
historical time-machine for a simple, linear, development cycle. In
these simple scenarios there is _NO_ "path" co-ordinate to manage,
since there are no branches at all: everything happens on the trunk
(yes, really!).
This comes back to my basic argument: _Simple_ uses of subversion
need a _simple_ way to symbolically track the timeline. Tags are not
simple. Hence labels. Simple labels are not suitable for non-linear
(read: anything except simple) dev cycles, and for that we have tags.
--Tim
On Nov 22, 2006, at 8:22 AM, Felix Gilcher wrote:
> John Rouillard <ma...@renesys.com> schrieb am Mittwoch, 22.
> November 2006 16:53:
>
>> On Wed, Nov 22, 2006 at 09:49:01AM +0100, Robert Graf-Waczenski
>> wrote:
>>>> 2. How many labels can be attached to a revision? One? Any number?
>>>
>>> Only one. (Remember, we're talking *poor* man's labels here...)
>>
>> So adding a new label to the rev destroys the old label? I think
>> this
>> is wrong. Any given revision should be able to have the same label.
>> Especially with mutable labels you may need to double label a
>> revision
>> with a permanent label (say PRODUCTION_2006_11_22) and a floating
>> lable (CURRENT_PRODUCTION).
>
> I see you're trying to replace tags by labels. You really should be
> aware that if a label is a revision alias it does not carry enough
> information to identify a production release. Regard subversion as
> a versioned filesystem. Every resource can be identified by 2
> coordinates: a paths and a time coordinate. Time is what you
> specify with the revision argument to the svn command unless HEAD
> is implied. So what does a label "PRODUCTION" mean if it references
> revision X? Is it
>
> componentY/stable/version1/ at revision X
>
> or maybe
>
> componentY/development/currently_broken/ at revision X
>
> Things get even worse when you have a repository as the apache
> foundation [1] has: all ASF projects from ANT to xmlgraphics are in
> a single repository - this is quite a common usecase. What does the
> label "PRODUCTION" mean in this context?
>
> So you'd have to specify
>
> svn co -r"APR_PRODUCTION" http://svn.apache.org/repos/asf/apr/apr/
> trunk/
>
> or something similar instead of
>
> svn co http://svn.apache.org/repos/asf/apr/apr/tags/1.2.7/
>
> Which one of the two is more error prone? Without a doubt the first
> one. What happens if you confuse which labels belong to which path
> of your project? You may get build errors or even worse build and
> release old, buggy versions. The current tagging mechanism is way
> more suited to identifying frozen revisions such as "PRODUCTION".
>
> So what I'm missing in this discussion is what exact benefits do
> you all expect from labels as revision ids? What about this:
>
> Make it possible to specify a svn url in the -r argument. If the
> argument is an url, it gets replaced by the revision in which the
> branch/tag was created. There are some corner cases (what happens
> if the url does not point to branch etc.), but it would be possible
> to create such an implementation as a shellwrapper to svn for
> testing purposes.
>
>
> regards
>
> felix
>
>
> [1] http://svn.apache.org/repos/asf/
>
> --
> 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
AW: Re: Simple Label=RevisionID Discussion
Posted by Felix Gilcher <gi...@exozet.com>.
John Rouillard <ma...@renesys.com> schrieb am Mittwoch, 22. November 2006 16:53:
> On Wed, Nov 22, 2006 at 09:49:01AM +0100, Robert Graf-Waczenski wrote:
>>> 2. How many labels can be attached to a revision? One? Any number?
>>
>> Only one. (Remember, we're talking *poor* man's labels here...)
>
> So adding a new label to the rev destroys the old label? I think this
> is wrong. Any given revision should be able to have the same label.
> Especially with mutable labels you may need to double label a revision
> with a permanent label (say PRODUCTION_2006_11_22) and a floating
> lable (CURRENT_PRODUCTION).
I see you're trying to replace tags by labels. You really should be aware that if a label is a revision alias it does not carry enough information to identify a production release. Regard subversion as a versioned filesystem. Every resource can be identified by 2 coordinates: a paths and a time coordinate. Time is what you specify with the revision argument to the svn command unless HEAD is implied. So what does a label "PRODUCTION" mean if it references revision X? Is it
componentY/stable/version1/ at revision X
or maybe
componentY/development/currently_broken/ at revision X
Things get even worse when you have a repository as the apache foundation [1] has: all ASF projects from ANT to xmlgraphics are in a single repository - this is quite a common usecase. What does the label "PRODUCTION" mean in this context?
So you'd have to specify
svn co -r"APR_PRODUCTION" http://svn.apache.org/repos/asf/apr/apr/trunk/
or something similar instead of
svn co http://svn.apache.org/repos/asf/apr/apr/tags/1.2.7/
Which one of the two is more error prone? Without a doubt the first one. What happens if you confuse which labels belong to which path of your project? You may get build errors or even worse build and release old, buggy versions. The current tagging mechanism is way more suited to identifying frozen revisions such as "PRODUCTION".
So what I'm missing in this discussion is what exact benefits do you all expect from labels as revision ids? What about this:
Make it possible to specify a svn url in the -r argument. If the argument is an url, it gets replaced by the revision in which the branch/tag was created. There are some corner cases (what happens if the url does not point to branch etc.), but it would be possible to create such an implementation as a shellwrapper to svn for testing purposes.
regards
felix
[1] http://svn.apache.org/repos/asf/
--
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
Re: Simple Label=RevisionID Discussion
Posted by John Rouillard <ro...@renesys.com>.
On Wed, Nov 22, 2006 at 09:49:01AM +0100, Robert Graf-Waczenski wrote:
> > 2. How many labels can be attached to a revision? One? Any number?
>
> Only one. (Remember, we're talking *poor* man's labels here...)
So adding a new label to the rev destroys the old label? I think this
is wrong. Any given revision should be able to have the same label.
Especially with mutable labels you may need to double label a revision
with a permanent label (say PRODUCTION_2006_11_22) and a floating
lable (CURRENT_PRODUCTION).
> > 3. When are labels attached? Using a discrete comment? Using a new
> > commit-time switch (which would need to include other "commit" type
> > commands like copy/import)?
>
> I'm not sure what you mean here. The label should be attachable any
> time to any revision that exists in the repo.
Then this argues for non-revisioned properties in which case multiple
labels may be even more important.
> > 5. If rev N has label X can ren M have the same label? How should the
> > tools behave in such a case when choosing a rev# based on label?
>
> That's something i actually overlooked. You are right, label texts must
> be unique, i.e. if rev N has label X, then rev M can not have the
> same label.
Initially yes there should be only one copy of a unique
label (as in CVS for example) on a file.
However we do have peg revisions in SVN so it is possible to start in
the middle of the revision tree and search backwards from that point
for the label.
E.G. on file http://.../foo.c
label revision
8
PRODUCTION 10
PRODUCTION 12
PRODUCTION 15
If I co/update
-r PRODUCTION http://.../foo.c
I get version 15. If I use:
-r PRODUCTION http://.../foo.c@14
I get revision 12
and
-r PRODUCTION http://.../foo.c@11
gets rev 10
-r PRODUCTION http://.../foo.c@9
gets nothing since there was no production tag prior to that point.
This provides a way to get at prior PRODUCTION tags and reconstruct
them.
> Moreover, i also overlooked the following, which does not directly
> apply to the PML label feature but rather to the way that for example
> the svn toolchain gives access to the label information:
>
> Say for example that file F1 has been changed at revs 7 and 15 and
> that HEAD currently is 18. Now i attach the PML "Rel 1.0" to rev 10
> and the PML "Rel 1.1" to rev 18. Now i want to see that F1 has seen
> changes at revs 7 and 15 (which is already supported via "svn log")
> and that there were labelled revisions *between* 7 and 15 and *after*
> 15. By piecing this information together, i know that the F1 change
> at rev 7 was released with release 1.0 of my product and that the
> F1 change at rev 15 has been released with 1.1, so if the F1 change
> at rev 15 introduced a bug, then i know that release 1.0 doesn't have
> the bug yet, which is what i'm aiming at.
>
> I'm thinking of a new subcommand (called for example "svn labels")
> which would quickly list all labels that have been set on the repo
> globally.
Or maybe just a flag to svn info?
--
-- rouilj
John Rouillard
System Administrator
Renesys Corporation
603-643-9300 x 111
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Simple Label=RevisionID Discussion
Posted by Mark Clements <gm...@kennel17.co.uk>.
"Tim Hill" <dr...@comcast.net> wrote in message
news:CD54170C-0194-43D9-A86D-B1BF743B0762@comcast.net...
>
> On Nov 22, 2006, at 12:49 AM, Robert Graf-Waczenski wrote:
>
> In fact, I think the answer is that you *can* have the same label
> reused multiple times. The default behavior should then be for
> Subversion commands to use the _newest_ instance of that label when
> it is specified in the --revision switch. This allows a newer re-use
> of the same label to "shadow" the earlier use. If you want to get the
> earlier label, you simply use a peg revision to get to the earlier
> part of the tree.
>
> Note that this also solves the mutable problem: labels can be re-used
> without needing to be mutable. Also, if you allow multiple labels per
> rev#, then I think there is _never_ a need to delete a label from a
> rev#.
>
Except to correct a mistake...
- Mark Clements
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Simple Label=RevisionID Discussion
Posted by Tim Hill <dr...@comcast.net>.
On Nov 22, 2006, at 12:49 AM, Robert Graf-Waczenski wrote:
>> ok, let's flesh out the details...
>>
>> 1. Label syntax: what are the allowed set of characters in a label?
>> Bear in mind that they need to be injected back into command-lines,
>> so there are some restrictions if they are going to be parsed
>> unambiguously.
>
> Even though i think that US-ASCII would be sufficient for my purposes,
> i don't see why full UTF-8 should cause problems even if it would be
> used in the command line. If commit messages are restricted to less
> than UTF-8 for this particular reason, then i'm fine with that.
I think at least a few "special" characters need to be disallowed
(e.g. double quotes) as otherwise parsing the command-line and/or
parsing any "svn list-labels" command becomes a nightmare.
>
>> 2. How many labels can be attached to a revision? One? Any number?
>
> Only one. (Remember, we're talking *poor* man's labels here...)
>
>> 3. When are labels attached? Using a discrete comment? Using a new
>> commit-time switch (which would need to include other "commit" type
>> commands like copy/import)?
>
> I'm not sure what you mean here. The label should be attachable any
> time to any revision that exists in the repo.
Sorry, I meant "discrete commit", i.e. set a label via "svn label"
command, rather than "svn commit ... -label ...". Of course, you
could have both.
>
>> 4. You are proposing mutable labels. Is this safe? Should the system
>> only allow a label to be changed if some sort of --force switch is
>> also supplied?
>
> Yes, labels should be mutable, they should be changeable without any
> additional --force switch being supplied. (However, i find that SVN's
> current default behavior of not allowing revision property changes
> without
> the pre-revprop-change commit hook being implemented would do well
> for handling label text changes.)
> Sure, if projects fiddle with the label texts and forget to adjust
> their build scripts, their builds will fail. But i don't think that
> this is a problem of SVN's. To SVN+PML(TM), a PML is a revision alias
> (which is enforced to be unique, see below), nothing more.
To an extent, I agree. BUT this is a significant departure from SVN
as it currently exists. Today, SVN gives a strong guarantee about the
behavior of past revisions. If, at one time, a rev# represented a
certain snapshot state of a project then the idea is that it _always_
represents that state. Thus, I can "wind-back" time and always (for
example) rebuild an older rev of a product, assuming I track/audit
the rev#s (which, I grant, would be easier with labels). Tags are an
explicit presentation of this concept.
There are only two ways today to break this contract: an admin can
delete a rev from a repo (but that's an admin thing, not a regular
user), or a revprop can be changed, but this is disabled by default
precisely because it breaks the snapshot contract.
>
>> 5. If rev N has label X can ren M have the same label? How should the
>> tools behave in such a case when choosing a rev# based on label?
>
> That's something i actually overlooked. You are right, label texts
> must
> be unique, i.e. if rev N has label X, then rev M can not have the
> same label.
In fact, I think the answer is that you *can* have the same label
reused multiple times. The default behavior should then be for
Subversion commands to use the _newest_ instance of that label when
it is specified in the --revision switch. This allows a newer re-use
of the same label to "shadow" the earlier use. If you want to get the
earlier label, you simply use a peg revision to get to the earlier
part of the tree.
Note that this also solves the mutable problem: labels can be re-used
without needing to be mutable. Also, if you allow multiple labels per
rev#, then I think there is _never_ a need to delete a label from a
rev#.
For example:
svn label "foo-lab" # Label the head revision (200) with "foo-lab"
svn label "rev150" --revision 150 # Label for rev 150
svn label "foo-lab" --revision 100 # Label a prior revision with
"foo-lab"
svn label "bar-lab" --revision 100 # .. and "bar-lab"
Now:
svn co foo.c -r "foo-lab" # Gets foo.c from rev 200
svn co foo.c -r "bar-lab" # Gets foo.c from rev 100
svn co foo.c@"rev150" -r "foo-lab" # Gets foo.c from rev 100
Note the last command: the peg-revision directs subversion to begin
searching at rev# 150, so the newest "foo-lab" in this case is rev 100.
I think the command-set for labels would pretty much match that for
revprops:
-- Command to set a label against a rev# (default, HEAD):
svn labelset <name> [--revision ...]
-- Command to get the rev# that corresponds to a label:
svn labelrev <name> [--revision ...] # --revision is used to
specify a start-point for the (backward) search (like a peg revision)
-- Command to list all labels in a rev# range:
svn labellist [--revision N:M] # Default N:M = 1:HEAD
Of course, the --revision switch could take labels as arguments.
Also, svn commands that display rev#s should be able to display
labels with the addition of a --label switch (so existing parsers
don't break).
Finally, since labels are global, the ability to _set_ them should be
under the control of the server. Either via a new authz declaration
(in addition to read, write and none), or via a hook script (or both).
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Simple Label=RevisionID Discussion
Posted by Nikki Locke <in...@trumphurst.com>.
Robert Graf-Waczenski wrote:
> > ok, let's flesh out the details...
> >
> > 1. Label syntax: what are the allowed set of characters in a label?
> > Bear in mind that they need to be injected back into command-lines,
> > so there are some restrictions if they are going to be parsed
> > unambiguously.
>
> Even though i think that US-ASCII would be sufficient for my purposes,
> i don't see why full UTF-8 should cause problems even if it would be
> used in the command line. If commit messages are restricted to less
> than UTF-8 for this particular reason, then i'm fine with that.
As the label is going to be used in the command line in place of a revision
number, presumably it cannot contain characters that are significant in shell
or svn command line parsing, including colon, brace ({) and space, and
probably it should not start with "-" (or, perhaps, any digit).
--
Nikki Locke, Trumphurst Ltd. PC & Unix consultancy & programming
http://www.trumphurst.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Simple Label=RevisionID Discussion
Posted by Robert Graf-Waczenski <rg...@lsoft.com>.
> ok, let's flesh out the details...
>
> 1. Label syntax: what are the allowed set of characters in a label?
> Bear in mind that they need to be injected back into command-lines,
> so there are some restrictions if they are going to be parsed
> unambiguously.
Even though i think that US-ASCII would be sufficient for my purposes,
i don't see why full UTF-8 should cause problems even if it would be
used in the command line. If commit messages are restricted to less
than UTF-8 for this particular reason, then i'm fine with that.
> 2. How many labels can be attached to a revision? One? Any number?
Only one. (Remember, we're talking *poor* man's labels here...)
> 3. When are labels attached? Using a discrete comment? Using a new
> commit-time switch (which would need to include other "commit" type
> commands like copy/import)?
I'm not sure what you mean here. The label should be attachable any
time to any revision that exists in the repo.
> 4. You are proposing mutable labels. Is this safe? Should the system
> only allow a label to be changed if some sort of --force switch is
> also supplied?
Yes, labels should be mutable, they should be changeable without any
additional --force switch being supplied. (However, i find that SVN's
current default behavior of not allowing revision property changes without
the pre-revprop-change commit hook being implemented would do well
for handling label text changes.)
Sure, if projects fiddle with the label texts and forget to adjust
their build scripts, their builds will fail. But i don't think that
this is a problem of SVN's. To SVN+PML(TM), a PML is a revision alias
(which is enforced to be unique, see below), nothing more.
> 5. If rev N has label X can ren M have the same label? How should the
> tools behave in such a case when choosing a rev# based on label?
That's something i actually overlooked. You are right, label texts must
be unique, i.e. if rev N has label X, then rev M can not have the
same label.
Moreover, i also overlooked the following, which does not directly
apply to the PML label feature but rather to the way that for example
the svn toolchain gives access to the label information:
Say for example that file F1 has been changed at revs 7 and 15 and
that HEAD currently is 18. Now i attach the PML "Rel 1.0" to rev 10
and the PML "Rel 1.1" to rev 18. Now i want to see that F1 has seen
changes at revs 7 and 15 (which is already supported via "svn log")
and that there were labelled revisions *between* 7 and 15 and *after*
15. By piecing this information together, i know that the F1 change
at rev 7 was released with release 1.0 of my product and that the
F1 change at rev 15 has been released with 1.1, so if the F1 change
at rev 15 introduced a bug, then i know that release 1.0 doesn't have
the bug yet, which is what i'm aiming at.
I'm thinking of a new subcommand (called for example "svn labels")
which would quickly list all labels that have been set on the repo
globally.
Tools such as TortoiseSVN could easily merge this information with
the current output of "svn log", yielding the information that i
need and reducing the need to issue "svn log" on the repo root or
on other non-trivial repo parts with lots and lots of
added/changed/deleted files, which is sometimes painfully slow!
Robert
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Simple Label=RevisionID Discussion
Posted by Tim Hill <dr...@comcast.net>.
ok, let's flesh out the details...
1. Label syntax: what are the allowed set of characters in a label?
Bear in mind that they need to be injected back into command-lines,
so there are some restrictions if they are going to be parsed
unambiguously.
2. How many labels can be attached to a revision? One? Any number?
3. When are labels attached? Using a discrete comment? Using a new
commit-time switch (which would need to include other "commit" type
commands like copy/import)?
4. You are proposing mutable labels. Is this safe? Should the system
only allow a label to be changed if some sort of --force switch is
also supplied?
5. If rev N has label X can ren M have the same label? How should the
tools behave in such a case when choosing a rev# based on label?
I think I know what I would answer to the above, just canvasing other
input.
--Tim
On Nov 21, 2006, at 6:29 AM, Robert Graf-Waczenski wrote:
> I *very much* second the proposal to start a discussion about
> simple labels. So, to get this right from the beginning, i'll
> first coin a snappy term and then describe the features i need:
>
> Poor Man's Label "PML"
> ----------------------
>
> 1) A PML can be attached to any existing revision, similar to
> revision properties.
>
> 2) If a PML was attached to a revision, then this PML can be
> used in any svn toolchain command as an alias for that specific
> revision and when the rev# is displayed in a history log, then
> the PML should be displayed next to it, if there is one.
>
> 3) Existing PMLs can be edited in any desirable way, including
> editing of the PML text and removing the PML.
>
> Robert
>
>> -----Original Message-----
>> From: Tony Harverson [mailto:tony.harverson@iglu.com]
>> Sent: Dienstag, 21. November 2006 14:14
>> To: Subversion Users
>> Subject: Simple Label=RevisionID Discussion
>>
>>
>>> -----Original Message-----
>>> From: Robert Graf-Waczenski [mailto:rgw@lsoft.com]
>>>
>>> Don't throw the word "branch" into this discussion! The issue
>>> at hand evolves around SVN's notion of "tagging" compared
>>> with various levels of a yet-to-be-defined support for
>>> labels, revision aliases, revision indexes or whatver else
>>> they have been called.
>> You're right, I meant "Tag" instead of "Branch". The Comment
>> should have read:
>>
>> "Yup, but that would be a tag, which is contended to be too
>> complex/complicated for non technical users or some of the projects
>> under discussion here. This discussion has the precept
>> that users do not want to copy off to another folder location, but
>> want
>> to replace that functionality with a labelling feature set which
>> is easier to use."
>>
>>> *don't* want to get rid of using branches! But still we would
>>> benefit from label support in SVN (in our case: from trivial
>>> repo-wide revision aliases, we don't need the more complex
>>> variants that others have described and which arguably
>>> overlap with what the SVN devs intended with the "tag" concept.)
>>
>> We desperately need to sever the various discussions in here,
>> because we're chasing our tails discussing blurry and moving
>> targets. *Your* requirement is for a simple revision = label
>> mapping. The comment I replied to was in reply to a discussion
>> about complex tags/labels, which is a semi-separate discussion.
>>
>> If the simplest concept of a label (revision ID = "Label") was
>> implemented, it would be useful for (for example) tagging the
>> stable and production versions of an ongoing project. It would
>> not, however, be useful for labelling releases, which seems to be
>> the other requirement which is being loaded onto it. ( For
>> reasons already covered in this thread, there's nowhere to commit
>> fixes to in the second case, and the requirement becomes for
>> complex tags, which is another discussion.
>>
>> T
>>
>> ---------------------------------------------------------------------
>> 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Simple Label=RevisionID Discussion
Posted by Robert Graf-Waczenski <rg...@lsoft.com>.
I *very much* second the proposal to start a discussion about
simple labels. So, to get this right from the beginning, i'll
first coin a snappy term and then describe the features i need:
Poor Man's Label "PML"
----------------------
1) A PML can be attached to any existing revision, similar to
revision properties.
2) If a PML was attached to a revision, then this PML can be
used in any svn toolchain command as an alias for that specific
revision and when the rev# is displayed in a history log, then
the PML should be displayed next to it, if there is one.
3) Existing PMLs can be edited in any desirable way, including
editing of the PML text and removing the PML.
Robert
> -----Original Message-----
> From: Tony Harverson [mailto:tony.harverson@iglu.com]
> Sent: Dienstag, 21. November 2006 14:14
> To: Subversion Users
> Subject: Simple Label=RevisionID Discussion
>
>
> > -----Original Message-----
> > From: Robert Graf-Waczenski [mailto:rgw@lsoft.com]
> >
> > Don't throw the word "branch" into this discussion! The issue
> > at hand evolves around SVN's notion of "tagging" compared
> > with various levels of a yet-to-be-defined support for
> > labels, revision aliases, revision indexes or whatver else
> > they have been called.
> You're right, I meant "Tag" instead of "Branch". The Comment
> should have read:
>
> "Yup, but that would be a tag, which is contended to be too
> complex/complicated for non technical users or some of the projects
> under discussion here. This discussion has the precept
> that users do not want to copy off to another folder location, but want
> to replace that functionality with a labelling feature set which
> is easier to use."
>
> > *don't* want to get rid of using branches! But still we would
> > benefit from label support in SVN (in our case: from trivial
> > repo-wide revision aliases, we don't need the more complex
> > variants that others have described and which arguably
> > overlap with what the SVN devs intended with the "tag" concept.)
>
> We desperately need to sever the various discussions in here,
> because we're chasing our tails discussing blurry and moving
> targets. *Your* requirement is for a simple revision = label
> mapping. The comment I replied to was in reply to a discussion
> about complex tags/labels, which is a semi-separate discussion.
>
> If the simplest concept of a label (revision ID = "Label") was
> implemented, it would be useful for (for example) tagging the
> stable and production versions of an ongoing project. It would
> not, however, be useful for labelling releases, which seems to be
> the other requirement which is being loaded onto it. ( For
> reasons already covered in this thread, there's nowhere to commit
> fixes to in the second case, and the requirement becomes for
> complex tags, which is another discussion.
>
> T
>
> ---------------------------------------------------------------------
> 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