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

RE: Subversion tagging

From: L. Wayne Johnson <wayne_at_zk.com>
Date: 2007-01-22 19:05:18 CET

>> -----Original Message-----
>> From: Steve Bakke [mailto:steven.bakke@amd.com]
>> Sent: Monday, January 22, 2007 9:03 AM
>> To: Kenneth Wood; users@subversion.tigris.org
>> Subject: Re: Subversion tagging
>>
>> Subversion has been billed as the ³successor² to CVS. Granted, there are
>> many things such as tags that work in a different way. However, why is
>> it
>> that some people take the attitude that the way subversion implements
>> tags
>> actually covers the valid use-cases people had under CVS. Tags
>> generally
>> are used for two types of things 1) a coherent release of a group of
>> things..
>> 2) An attribute or indication of quality on individual files which may or
>> may not be coherent as a group.
>>
>> Please at least admit the fact that Subversion tags do not really
>> implement
>> the use-case of identifying the ³status² of a set of files. You can use
>> Subversion tags for this, but it¹s really just an approximation. For
>> instance, I would really like subversion to support this use-case:

I'll admit that I don't understand this use case, maybe because I only use
svn for source code projects (all the things under source code control work
together.) If all the files work together it not clear to me how you can
know the 'quality' of a single file in the collection since they are all
interrelated. And even if you can there is no guarantee that the file will
do what you want when matched up to files of a known 'quality' from a
different time. To me, the quality of a single file just doesn't count. My
customer doesn't care whether or not foo.c works correctly or not. My
customer only cares that when he runs my software he gets the "right
answer."

To be honest, I have seen processes where releases were built from arbitrary
versions of files. It seemed to me that an inordinate amount of time was
spent pulling things together, getting them to build and testing them.
Schedules slipped and the quality of the final product suffered. (Note to
self: Add this to the list of question asked to potential employers, "What
does your release process look like?")

The original poster asked for a way to pick a bunch of files from different
times in the source code development without having to go pick them all one
by one. I don't understand how you can pick a bunch of unconnected things
without picking each one by hand.

Subversion doesn't keep track of files, it tracks groups of files. It seems
to me that this was a conscious design decision and that with source code
projects, this is what you really want to do. I am not an expert in how svn
works but from what I understand it seems that adding support to track files
individually would be difficult at best.

There are some people that use subversion for tracking unrelated documents.
I don't think that Subversion was really not designed to do this.
 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jan 22 19:06:04 2007

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