Andrew Close wrote:
> On 5/9/07, david x callaway <dxc@pobox.com> wrote:
>> if you look at "all the possible solutions available", you will never
>> choose because there are at least dozens and maybe more. my advice
>> is to evaluate systems until you find at most 3 that meet your known
>> needs (including future), then stop looking and pick one. unless you
>> are really, really special I don't think it would be difficult to
>> come up with three good candidates.
>>
>> I'll even seed the flamewar: look at git, svn and perforce. like
>> gigantic systems that require multiple adminstrators? substitute
>> clearcase for one of the above. don't care about atomic commits and
>> speed of remote diffing? substitute cvs for one of the above.
>
> i'd be quite happy with SVN, and i think we could build a successful
> process around it. unfortunately it looks like management wants
> process in a box, which is particularly frustrating because then the
> developers have very little say in the process. we (the developers)
> know the current process is broken and would really like to be
> involved in fixing it. but we don't currently have an argument that
> will persuade management...
>
You could present a proposal that is tool agnostic. The proposal would
outline the risks inherent in the current process and toolset. Then you
describe a tool agnostic process that eliminates the risks. All that
remains is to show (in another document/presentation) which tools fit
the process well. This is the process I've followed here and combined
with a grass-roots concensus approach, seems to be working. Even if
they don't accept SVN, if the tool that's eventually chosen fits your
new process, then y'all will be OK. It is important not to get into
toolset disccusions until the new SCM process is defined. Otherwise,
it's the old "cart before the horse" scenario.
Will Appleton
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu May 10 17:45:24 2007