From: Laurent P. <lp...@sq...> - 2003-01-24 13:15:00
|
From: "Jeroen Latour" <jl...@ca...> > I cannot guarantee that there will never be a major bug that will > compromise your database, but I've been using CVS in production for a year, > without any problems. Usually, if a commit breaks something, it's fixed > pretty quickly. OK. Your answer sounds sufficiently confident for me. > >2- use the cvs version for an existing project. But Are the database upgrade > >scripts up to date for that ? > > They should be. Test them! (But backup!) OK too, I didn't want to upgrade if there was a 100% chance for the upgrade to crash, but with this assurance from you, I will test. And Oh, of course, backup is my friend :) > >3- Try and test the cvs version on a Test project only, because we don't > >have yet sufficient confidence in the potential risks of breaking the > >database integrity ? > > For translation work, you could just run it on a test project, but you'd > miss out on all the new features in CVS. It's your call :) > > >And there's no problem with diff, I can manage it. > > Good! 'cvs diff -u' is your friend. OK, thanks -- Laurent. |