Re: list of all files when tagging

> Our procedure of creating tags is to branch
> off the trunk for the preparation of a release. When all other files are
> changed or added, a final review is being held to check if the release is
> complete and without errors. Only after this review, a tag is created from
> that branch.

This is usually known as releasing off of a branch, and is probably
the most common way projects do their releases.

> The problem is, that when looking at the log of that tag, the files
> describing this tag are not listet. All it says is:
> action path copied from
> revision
> added .../tags/name .../branches/preparation_name
> XX

Welcome to the wacky world of Subversion tagging. In a revision
control system, tags in CVS are applied on each and every file.
Because of this, most sites want to see what individual files have
been tagged just to make sure none were skipped or mistagged.

However, Subversion doesn't tag individual files, but a whole batch of
files at once. In this case, you're tagging a branch, and a specific
revision on that branch. We do the same, so here's an example we have:

$ svn log --stop-on-copy -v
http://subversion/dev/modules/adsuite/tags/ADS-5.3.1.1
------------------------------------------------------------------------
r53910 | svnant | 2009-06-26 16:08:11 -0400 (Fri, 26 Jun 2009) | 1 line
Changed paths:
   A /modules/adsuite/tags/ADS-5.3.1.1 (from
/modules/adsuite/branches/5.3.1.1:53909)

Blah, blah, blah
------------------------------------------------------------------------

Take a quick look at my tag: It tells me that the tag was created off
the 5.3.1.1 branch on revision 53909. That happens to be the revision
of the branch we tested and certified as our release. Just by looking
at that, I can tell that the tag is good, and I can use that tag to
duplicate exactly what I released.

There's really no reason to review all the individual files that were
"tagged" because the files themselves weren't tagged. The whole branch
at that revision was tagged. It is impossible to miss tagging a
particular file or tagging the wrong revision of it..

> I would like to have a complete overview of all files contained in the
> folder ".../tags/name" so that I am able to use the search pannel of TSVN to
> find files contained in more than one release. Is that possible with SVN?

Subversion can help you find this information, but you'll have to
parse that information via some sort of scripting tool. For example,
let's say I determined that REL-1.0 was revision 12345 off of
svn://repos/foo/branches/1.0 and REL-1.1 was revision 23456 off of
svn://repos/foo/branches/1.0. Doing this will give me a list of all
files that were changed:

     $ svn -r12345:23456 log -v svn://repos/foo/branches/1.0

It will also list all commit comments, and whether the file was added,
deleted, moved, etc. Plus, if a particular file was changed more than
once, it will be duplicated on this list. A little parsing via a
scripting language (or even better a scripting language that uses the
Subversion API) will give me a list of exactly which files changed.

Is this what you are looking for?

On Mon, Jul 20, 2009 at 2:28 AM, Justus
Stadler_external<Justus.Stadler_external_at_de.kspg.com> wrote:
>
> Hi guys,
>
> I have a question about tagging. Our procedure of creating tags is to branch
> off the trunk for the preparation of a release. When all other files are
> changed or added, a final review is being held to check if the release is
> complete and without errors. Only after this review, a tag is created from
> that branch.
> The problem is, that when looking at the log of that tag, the files
> describing this tag are not listet. All it says is:
> action                path                copied from
>  revision
> added                .../tags/name        .../branches/preparation_name
>    XX
> I would like to have a complete overview of all files contained in the
> folder ".../tags/name" so that I am able to use the search pannel of TSVN to
> find files contained in more than one release. Is that possible with SVN? So
> far I helped myself by creating a list of all files and copying that list to
> the log message. But I hope there is an easier way to achieve this goal.
>
> Thanks for any help
> Justus
>
> Ps: I also posted this to the TSVN mailing list, because I'm not shure where
> this belongs.
>

-- 
David Weintraub
qazwart_at_gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2372609
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].