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

Re: Maintaining File/Directory lifecycle information

From: Andy Levy <andy.levy_at_gmail.com>
Date: Wed, 20 Aug 2008 07:16:58 -0400

On Wed, Aug 20, 2008 at 04:10, ChristianD2008
<christian.jungkind_at_kopfweb.de> wrote:
>
>
>> IMO you're approaching this from the wrong angle. You're thinking
>> about properties of specific files. Subversion manages versions of
>> directory trees (50,000-foot level view).
>
> When dealing with big software products and modular development, you
> need the module level information in order to keep overview:
> - you want to keep track of module (i.e. subdirectory) status:
> working, tested, released
> - when looking at the whole project (where the module might be
> included as externals), you would be interested in the status of all
> modules

You probably didn't mean it this way, but when written (no voice
inflection, etc.) this has a very condescending tone.

> To my opinion, it is not enough to provide a general project status
> using tags / branches.

Then break your project up into separate trees in your repository, and
then compose your project using svn:externals. Then you *can* monitor
the project status via tags & branches, using the facilities already
built into the system.

Subversion is not designed to manage projects via the metadata you're
proposing to invent.

> One thing to support this better would be an option to show custom
> attributes in Windows Explorer. Is this possible?

Vista can't even show the Subversion property columns, IIRC. So even
if that support appeared, it'd start to disappear.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-08-20 13:17:09 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.