>> -----Original Message-----
>> From: Byron Brummer [mailto:email@example.com]
>> Sent: Monday, January 22, 2007 5:27 PM
>> To: L. Wayne Johnson
>> Cc: firstname.lastname@example.org
>> Subject: Re: Subversion tagging
>> L. Wayne Johnson wrote:
>> >>>> I really would like to understand here but I can't imagine why you
>> >>> would
>> >>>> want to tag something other than what some developer is working on
>> >>>> his/her working copy.
>> >>> Because software rarely is a single machine. More often then not
>> >>> it's a collection of machines that may or may not talk to each
>> >>> other at various moments in time. It is invalid to believe because
>> >>> the radio isn't working that the engine won't start. Sure, they
>> >>> are both parts of the car, and maybe the changes to the radio were
>> >>> made first...
>> >>> But who really cares that the fixes to the carburettor weren't
>> >>> developed against the old version of the radio? The radio can
>> >>> wait,
>> >>> the carb can't.
>> > I wouldn't care. That's why I wouldn't tie the release of one with the
>> > at all. I think that if I had 2 things so different that I wouldn't try
>> > associate them in my source code control...
>> At the end of the day you're shipping the *car*. The car is the
>> configuration, as a whole. You aren't shipping the car in parts.
Like I said I don't have any more to contribute to this thread.
>> What would you do instead? Roll back your changes each time and
>> try again from scratch so that when it finally passes it would be
>> in a single tidy revision?
No I would bitch and moan at people who were donating their personal time to
help me out...
Nobody said SVN is perfect. It is what it is. You can either work with it or
beat your head against it. It's your choice.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue Jan 23 03:15:06 2007