You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Ilan Yaniv <Il...@timetoknow.org> on 2008/11/17 10:02:45 UTC
Using Tag methodology
Hi All,
I have this problem:
We have one SVN server with 2 repositories.
Our Production environment looks like hell for CM.
1) There is one version for the Server.
2) There are hundreds versions of clients.
3) There is even more versions of XML to be loaded on clients and
many binaries - including flesh, PDF, SWF files.
1) In order to manage a version in production, I need one label \ tag
that contains all data in both repositories.
2) I also need a label which is moveable, like "ready for QA" etc.
3) I want to create a branch which is based on a label that I create.
4) I want to be able to move a label on one revision of a file, without
changing the label on other files.
I know that all could be easily done using Star Team as CM tool. Could
it be done by SVN?
Ilan Yaniv
Configuration Management
Phone: 03-7534333 ext. 5873
Ilan.Yaniv@timetoknow.org
RE: Re: Using Tag methodology
Posted by Bob Archer <Bo...@amsi.com>.
Wow, that is a brilliant idea. I may use that. Almost like a symlink.
You can tag each release and then have a "QA Latest" folder that just
contains an external to one of the tags... wow... glad I'm on this list.
BOb
-----Original Message-----
From: Larry Shatzer, Jr. [mailto:larrys@gmail.com]
Sent: Monday, November 17, 2008 6:36 PM
To: kmradke@rockwellcollins.com
Cc: David Weintraub; Bob Archer; Ilan Yaniv; Ryan Schmidt; Trevor
Harmon; Subversion Users
Subject: Re: Re: Using Tag methodology
On Mon, Nov 17, 2008 at 4:26 PM, <km...@rockwellcollins.com> wrote:
>
> One of the "nice" things about floating labels is that I know
> "APPROVED_QA" is always the latest one, I don't need to manually
> search "tags/QA/..." for the "last" one...
>
> (And yes, you could have an "APPROVED_QA" tag that is deleted and
> recreated every time a -xxx one is created, but that is a pain.)
>
Or you can create a svn:external to the right location (even based on
revision), and keep updating that as needed.
-- Larry
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Re: Using Tag methodology
Posted by km...@rockwellcollins.com.
"Larry Shatzer, Jr." <la...@gmail.com> wrote on 11/17/2008 05:35:59 PM:
> On Mon, Nov 17, 2008 at 4:26 PM, <km...@rockwellcollins.com> wrote:
> >
> > One of the "nice" things about floating labels is that I know
> > "APPROVED_QA" is always the latest one, I don't need to manually
> > search "tags/QA/..." for the "last" one...
> >
> > (And yes, you could have an "APPROVED_QA" tag that is deleted and
> > recreated every time a -xxx one is created, but that is a pain.)
> >
>
> Or you can create a svn:external to the right location (even based on
> revision), and keep updating that as needed.
Creating an svn:external instead of a fully populated tag with a
lightweight copy is an interesting idea. Still requires the
user/script to do 2 actions (create tag, update external props),
instead of just 1 action (update tag).
I personally like the idea of keeping past revisions of a
"floating tag" available, but convincing others to do
more work for functionality they don't think they need
usually proves futile...
Kevin R.
Re: Re: Using Tag methodology
Posted by "Larry Shatzer, Jr." <la...@gmail.com>.
On Mon, Nov 17, 2008 at 4:26 PM, <km...@rockwellcollins.com> wrote:
>
> One of the "nice" things about floating labels is that I know
> "APPROVED_QA" is always the latest one, I don't need to manually
> search "tags/QA/..." for the "last" one...
>
> (And yes, you could have an "APPROVED_QA" tag that is deleted and
> recreated every time a -xxx one is created, but that is a pain.)
>
Or you can create a svn:external to the right location (even based on
revision), and keep updating that as needed.
-- Larry
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Using Tag methodology
Posted by Lorenz <lo...@yahoo.com>.
David Weintraub wrote:
>[...]
>The problem with the floating tag is what happens if you have to move
>back in time. What was your previous QA release? What if you discover
>a new bug in your QA release and you want to know what changed between
>one QA release and another. You can't with a floating tag because you
>lost your history.
you can always look at the log of the tags-folder to see what happend
to your floating tag in the past.
--
Lorenz
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Using Tag methodology
Posted by Les Mikesell <le...@gmail.com>.
David Weintraub wrote:
> >
> The problem with the floating tag is what happens if you have to move
> back in time.
That's a problem solved by floating tags, not caused by them. Just
float your "current-2" tag to the "current-1" postition, "current-1" to
"current, and set a new "current" at the tested workspace version.
> What was your previous QA release?
If you can float that tag, you always know that without tracking any
changing names or numbers.
> What if you discover
> a new bug in your QA release and you want to know what changed between
> one QA release and another. You can't with a floating tag because you
> lost your history.
You don't lose anything because the history exists apart from the tags.
The tags just identify interesting sets of revisions so you can script
all the obvious things you are likely to want to do with them without
having to pick up variable revision identifiers at runtime.
--
Les Mikesell
lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Re: Using Tag methodology
Posted by David Weintraub <qa...@gmail.com>.
On Mon, Nov 17, 2008 at 6:26 PM, <km...@rockwellcollins.com> wrote:
>
> "David Weintraub" <qa...@gmail.com> wrote on 11/17/2008 03:06:25 PM:
> ...
>> In most revision control software a label "APPROVED_QA" would not tell
>> you what was the previous revision that was approved for QA or what
>> the difference is between this QA revision and the last, or when this
>> revision was approved for QA. By using Subversion and getting rid of
>> floating labels, you no longer have this problem.
>
> One of the "nice" things about floating labels is that I know
> "APPROVED_QA" is always the latest one, I don't need to manually
> search "tags/QA/..." for the "last" one...
>
> (And yes, you could have an "APPROVED_QA" tag that is deleted and
> recreated every time a -xxx one is created, but that is a pain.)
>
> This concept is really no different than "HEAD" is today, just
> with greater flexibility.
If you really want a floating tag, why not just treat APPROVED_QA as a
branch instead of a tag. Merge your changes onto the APPROVED_QA "tag"
and commit them. We do something similar with our webpage deployments.
We have our development on trunk, then when we are ready to deploy,
copy it to our QA server branch, and then to our PROD branch.
Or, just do the delete/copy tag operation anyway. You can delete and
add a tag in Subversion faster than you can retag your files in any
other revision control system on the market.
The problem with the floating tag is what happens if you have to move
back in time. What was your previous QA release? What if you discover
a new bug in your QA release and you want to know what changed between
one QA release and another. You can't with a floating tag because you
lost your history.
The main reason we used a floating tag was the difficulty in just
finding out what is the latest release. In almost all revision control
systems, you either have to find that special file that existed in
each and every release and was labeled in each and every release, or
get a listing of all the tags on all the files, and combine them into
a single super list. The first took special knowledge of your project,
and the second could take quite a while to perform.
In Subversion, finding the last label created is easy. Our development
and QA people know where to find that information. We simply don't
need to mark the last build or the last QA release with a special
floating tag anymore.
--
David Weintraub
qazwart@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Re: Using Tag methodology
Posted by km...@rockwellcollins.com.
"David Weintraub" <qa...@gmail.com> wrote on 11/17/2008 03:06:25 PM:
...
> In most revision control software a label "APPROVED_QA" would not tell
> you what was the previous revision that was approved for QA or what
> the difference is between this QA revision and the last, or when this
> revision was approved for QA. By using Subversion and getting rid of
> floating labels, you no longer have this problem.
One of the "nice" things about floating labels is that I know
"APPROVED_QA" is always the latest one, I don't need to manually
search "tags/QA/..." for the "last" one...
(And yes, you could have an "APPROVED_QA" tag that is deleted and
recreated every time a -xxx one is created, but that is a pain.)
This concept is really no different than "HEAD" is today, just
with greater flexibility.
Most other systems also have some way to query the label history,
so label moving isn't a major tracking problem as you
alluded to.
With Subversion it is also quite difficult to see who else
is using the same (or other versions) of the same shared
file. Most CM systems make this trivial...
Kevin R.
Re: Re: Using Tag methodology
Posted by David Weintraub <qa...@gmail.com>.
I actually find that I don't need floating labels in Subversion as we
did in other revision control systems.
In most revision control systems, tags are on individual files, and it
is difficult to find the tags and then figure out which one you're
interested in. Thus, many sites needs labels to say that this is the
QA release, or this is a candidate release.
However, in Subversion, tags are done on a directory tree basis and
not on a file-by-file basis. Not only that, but its very easy to see
what tags are out there because tags are external directory structures
and not internal to each individual repository file.
Remember too that the tags directory structure isn't set into stone.
For example, we have three sub-directories in our tags directory: DEV,
QA, and REL. All QA releases tags are stored in the QA folder, so it's
easy to see what releases have been approved for QA. We simply copy
the tag approved for QA from the DEV folder to the QA folder.
For example, imagine our directory structure looks like this:
.../tags/DEV/FOO-1.4-D-001
.../tags/DEV/FOO-1.4-D-002
.../tags/DEV/FOO-1.4-D-003
.../tags/QA/FOO-1.4-Q-001
.../tags/QA/FOO-1.4-Q-002
.../tags/REL/FOO-1.4.1
.../tags/REL/FOO-1.4.2
It's easy to see that the last QA release is FOO-1.4-Q-002, and you
can get that with a simple "svn ls" command. Need to know what release
FOO-1.4-Q-002 is based upon? Just run the following command:
$ svn log --stop-on-copy -v http://[...]/tags/QA/FOO-1.4-Q-002
------------------------------------------------------------------------------------------------------------
r20961 | svnant | 2008-11-10 09:38:11 -0500 (Mon, 10 Nov 2008) | 1 line
Changed paths:
A /[...]/tags/QA/FOO-1.4-Q-002 (from /.../tags/DEV/FOO-1.4-D-003:20960)
Now, it's easy to see that FOO-1.4-Q-002 was based upon FOO-1.4-D-003
and that this tag was created on Nov, 11, 2008. There is even a
comment (not shown) which could include even more information.
One of the hard things to do when you use new software is to get out
of old habits that you use to do because there was no better way of
handling the situation. There really isn't any need for floating
labels since it is so easy to get what you want and it has a lot more
meaning too.
In most revision control software a label "APPROVED_QA" would not tell
you what was the previous revision that was approved for QA or what
the difference is between this QA revision and the last, or when this
revision was approved for QA. By using Subversion and getting rid of
floating labels, you no longer have this problem.
--
David Weintraub
qazwart@gmail.com
On Mon, Nov 17, 2008 at 2:40 PM, Bob Archer <Bo...@amsi.com> wrote:
> No.. I don't think that's what he wants. He doesn't want to "move" the
> tag folder itself but have the same tag contain different revisions of a
> file. Sort of like "float" label. The only way to do this is..
>
> 1. Delete the tag and do a new copy using the same tag name.
> 2. Commit changes directly to the tag folder. Basically goes against the
> tag convention but is doable.
>
> Bob
>
>
> -----Original Message-----
> From: Trevor Harmon [mailto:trevor@vocaro.com]
> Sent: Monday, November 17, 2008 11:46 AM
> To: Ryan Schmidt
> Cc: Ilan Yaniv; Subversion Users
> Subject: Re: Using Tag methodology
>
> On Nov 17, 2008, at 5:40 AM, Ryan Schmidt wrote:
>
>>> 2) I also need a label which is moveable, like "ready for QA" etc.
>>
>> Since tags are just copies, to recreate a tag, you would first
>> delete the old tag, then create the new tag. You can do this with a
>> normal Subversion client, and it will result in two revisions (one
>> to delete and one to create)
>
> Couldn't he just do a "move" on the tag? I thought tags are like any
> other directory in Subversion, which means they can be moved around.
>
> Trevor
>
>
> ---------------------------------------------------------------------
> 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: Re: Using Tag methodology
Posted by Bob Archer <Bo...@amsi.com>.
No.. I don't think that's what he wants. He doesn't want to "move" the
tag folder itself but have the same tag contain different revisions of a
file. Sort of like "float" label. The only way to do this is..
1. Delete the tag and do a new copy using the same tag name.
2. Commit changes directly to the tag folder. Basically goes against the
tag convention but is doable.
Bob
-----Original Message-----
From: Trevor Harmon [mailto:trevor@vocaro.com]
Sent: Monday, November 17, 2008 11:46 AM
To: Ryan Schmidt
Cc: Ilan Yaniv; Subversion Users
Subject: Re: Using Tag methodology
On Nov 17, 2008, at 5:40 AM, Ryan Schmidt wrote:
>> 2) I also need a label which is moveable, like "ready for QA" etc.
>
> Since tags are just copies, to recreate a tag, you would first
> delete the old tag, then create the new tag. You can do this with a
> normal Subversion client, and it will result in two revisions (one
> to delete and one to create)
Couldn't he just do a "move" on the tag? I thought tags are like any
other directory in Subversion, which means they can be moved around.
Trevor
---------------------------------------------------------------------
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: Using Tag methodology
Posted by Trevor Harmon <tr...@vocaro.com>.
On Nov 17, 2008, at 5:40 AM, Ryan Schmidt wrote:
>> 2) I also need a label which is moveable, like “ready for QA” etc.
>
> Since tags are just copies, to recreate a tag, you would first
> delete the old tag, then create the new tag. You can do this with a
> normal Subversion client, and it will result in two revisions (one
> to delete and one to create)
Couldn't he just do a "move" on the tag? I thought tags are like any
other directory in Subversion, which means they can be moved around.
Trevor
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Using Tag methodology
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Nov 17, 2008, at 04:02, Ilan Yaniv wrote:
> We have one SVN server with 2 repositories.
>
> Our Production environment looks like hell for CM.
> 1) There is one version for the Server.
> 2) There are hundreds versions of clients.
> 3) There is even more versions of XML to be loaded on clients
> and many binaries – including flesh, PDF, SWF files.
>
> 1) In order to manage a version in production, I need one label \
> tag that contains all data in both repositories.
Subversion doesn't have labels, and what it calls tags and branches
are just copies (though they are cheap copies, so they don't take up
lots of space). So to be able to tag something, you need to be able
to copy it. And Subversion can only copy within a repository, not
across repositories.
At least, that used to be true, but I seem to remember some changes
being made to allow cross-repository copying, either in Subversion
1.5.x or in what will be Subversion 1.6. However, it probably won't
be space-efficient.
> 2) I also need a label which is moveable, like “ready for QA” etc.
Since tags are just copies, to recreate a tag, you would first delete
the old tag, then create the new tag. You can do this with a normal
Subversion client, and it will result in two revisions (one to delete
and one to create); if it's important that there is no revision in
which the tag does not exist, use svnmucc to do both operations in a
single revision.
> 3) I want to create a branch which is based on a label that I create.
You would simply copy the existing tag URL to the desired new branch
URL.
> 4) I want to be able to move a label on one revision of a file,
> without changing the label on other files.
In Subversion there is no such thing as a label on a revision of a
file. In fact there is no such thing as a revision of a file.
Instead, there is such a thing as a file as it exists in a certain
revision of the repository. (Revisions are repository-global, not per-
file.) So in Subversion terms, you're asking to remove a file from a
tag and replace it with a newer version of that file. You could do
this as under (2) above, removing the old file and copying the new
one (either as separate revisions using svn or as one using svnmucc).
By convention, tags are generally supposed to be write-once entities;
you create them and then never modify them. But don't let that stop
you if you want to treat them as labels. You may however want to
merge instead of re-copying. And then what you're really talking
about is a branch, not a label or a tag.
> I know that all could be easily done using Star Team as CM tool.
> Could it be done by SVN?
I think the same end result can be achieved, though the concepts are
different. Reading the Subversion Book should help you understand how
it's all meant to work.
http://svnbook.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org