Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to firstname.lastname@example.org.
On Feb 11, 2008 11:39 PM, Arthur Barrett <arthur.barrett at march-hare.com> wrote: > <snip> > > > CVSNT 2.5.03 is as different to CVSNT 2.0.5 as SVN is to CVSNT. > > CVSNT 2.5.03 has rename support, mergepoints, failsafe audit, e-mail > integration, changesets, atomic checkout etc etc - most of which SVN > does not. > > Upgrade to CVSNT 2.5.03 and start using the new features then see if you > still require migration (you probably will not). Thanks for your reply. I used to manage my code with different SCM and know the issues... under linux. Nowadays, my boss want to switch to SVN... it is not a point to discuss. So, I am just looking at how can I do that. If only we were on linux.... no pb at all, cvs2svn works perfectly, no need of e-mail integration, nor fail safe audit, light scripting and powerful shell provide everything possible.... but we are running a dumb windows server. And I read on tigris website that migration from CVSNT may fail or work partially. So I decided to run tests with a few binaries and text files into a CVSNT server and try a migration. But to be relevant, my tests require the same version of our current CVSNT server.... but if no more info is written down into the repository with latest v2.5, I can use v2.5 instead for sure. If information are not exactly the same, I need a v2.0.5 server.... > There was a great article on the valuation of IT assets published in The > Financial Times UK Edition 36,501 on Monday October 1 2007, and I > believe the author will be releasing the complete whitepaper soon. > Basically it talks about the lack of business cases for the benefit of > software and also the business case for maintaining legacy assets. The > costs of replacing software like CVS for SVN are astronomical and rarely > worth it to the business, except perhaps that techie employees who like > playing with the latest gadgets are less likely to leave that week/month > for some other company, thereby reducing employee turnover. It is true that 'migrate for pleasure' is painful in business. But on a stable linux system, no problem at all to leave CVS for SVN. No problem with developers -they have already used SVN too- in my case. > When choosing any software tool it is best to know what features you > require and then look for the tool that offers those features, or even > better look for what your goals are, then look for a process that > supports that, then look for tools that can implement that process. For > instance knowing 'what' changed may be useless without knowing what else > changed - so you need to relate changes to one another and maybe > external events like project tasks, bugs or something else: so you would > need tools that support changesets and links to a system that tracks > those external events. True. The dpt leader is a professional too, who knows what SVN and CVS are... > When replacing one system with another it is important to know the real > value to the business that the change will bring, and the total cost of > that change relative to the total benefit to the business. See the > abovementioned FT article for more information. No need to see, I know. But it is not my decision, even if I thought that such a migration had a very low priority... I have to do it now. > I do not believe you will get any value from moving from CVSNT to SVN. > If there is something in particular you require, why not support the > product that has supported you for so many years and let the community > know what those features are and why you need them? As said earlier, my boss want and it is sufficient :) . It is possible to migrate. He prefers that we use SVN. He budget for it. We will do it. Rgds, Gal'