On 27/2/03 13:06, "Berin Loritsch" <[EMAIL PROTECTED]> wrote:
>> Subversion _will_ solve this issue, that's for sure, so my suggestion would >> be to move over onto that system, but there are IMHO, still issues with the >> availability of non-command line clients. I would wait to start using it >> until <http://tortoisesvn.tigris.org/> doesn't start working properly and it >> gets more widely deployed (I'm watching that space because we want to use it >> at VNU). > > I am not afraid of the command line, but there were issues with the > release of the Windows client the last time I messed with it. When run > on XP, it would fail miserably (core dump or something, can't quite > remember). The information on the server was OK, but sometimes I had to > make a commit more than once. > > I would like to see SubVersion improve a bit before making everyone > switch. The client reliability issue is what has me gun shy about it. > (No issues with the server that I can tell). And no issues in UNIX AFAICS... We (VNU) have already planned the adoption of SVN as our backend repository for a number of reasons (the primary one being that we will use it as our distributed filesystem, having our web applications deployed from a URL like http://svn.vnunet.com/app/live )... Basically, no more checkouts, no more scripts, you apply the change to the repository, and then it will go live straight away... But as for you, for us the client is _damn_ important... And we need not only to think about UNIX (server side), but with windows (JSPs amd XML writers) and with MacOS/9 and X (all our graphics production team)... We're testing hard on the baby, it's not quite there yet, but looks so promising to us that we're investing quite a good amount of time on it.. Pier
