| |||||||||||||
A proposed Subversion vision and roadmapA proposed Subversion vision and roadmapPosted Apr 5, 2010 22:07 UTC (Mon) by marcH (subscriber, #57642)In reply to: A proposed Subversion vision and roadmap by sitaram Parent article: A proposed Subversion vision and roadmap
> But I also think that in a typical corporate environment (which they now claim to be their main target market) this is far more likely to be management failure and a "that's the way we've always done it" attitude than any *real* need.
A good reason to use SVN is (was?) maturity. Not sure about now but a few years ago there was already a number of great SVN GUIs while the git CLI was still evolving.
Once SVN is here and does the job, depending on the "real needs" there can be very little reason for a costly migration. Migration cost is not just about finding a silver "svn2git" bullet, it's also about re-writing build scripts, training users, etc.
(Log in to post comments)
A proposed Subversion vision and roadmap Posted Apr 6, 2010 9:07 UTC (Tue) by sitaram (subscriber, #5959) [Link]
I quite agree about "very little reason for a costly migration".
However, that is a far cry from statements like "In short, they desperately need Subversion" :-)
A proposed Subversion vision and roadmap Posted Apr 6, 2010 19:54 UTC (Tue) by vonbrand (subscriber, #4458) [Link]
For the individual developer, Just wait; once the SVN lovers die out, you can just anoint a random clone into central repository rôle ;-)
|
|||||||||||||