>> > I really would like to understand here but I can't imagine why you
>> > want to tag something other than what some developer is working on in
>> > 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
>> the carb can't.
I wouldn't care. That's why I wouldn't tie the release of one with the other
at all. I think that if I had 2 things so different that I wouldn't try to
associate them in my source code control...
Look, I am not trying to say that your process is wrong. Maybe subversion is
the wrong tool for your process. Clearly subversion has warts but there are
several things that just seem right to me.
1.) Atomic commits. This allows me to add a feature or fix something and
check in *all* the changes at the same time. Some times this involves a
single file but sometimes it takes more than one. Either way I know that the
changes in between revision x and revision y contain *all* of the changes
required to address feature/bug n.
2.) The projects that I work on consist of a bunch of interrelated files.
Subversion keeps track of things as a group and not individually. It seems
to match the work flow.
Some have argued that tools should not impose process but in fact they do.
If you want a CVS style process then maybe CVS is the best tool for you.
I don't claim to be an expert on SVN or configuration management. It is
something that I am trying to learn about. I have learned a lot from this
list. Since I don't have anything relevant to contribute and I've learned
about as much as I can from this thread I'll be dropping out.
I do hope that you find an adequate solution for your process.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue Jan 23 01:51:31 2007