From: William D. <wi...@fl...> - 2004-05-17 08:22:23
|
Ian Bicking <ia...@co...> writes: > On May 16, 2004, at 4:12 AM, William Dode wrote: >> To don't rely more on *any* server, we could switch to Arch, we'll hav= e >> the same benefits as subversion for moving files, and somes more : to >> create distributed and independants branchs. >> Don't you like to can commit when you are away with your laptop ? >> We'll also don't need to give a write access to everybody who want a >> sandbox... (we are 61 developers !!!) > > This is a good argument against decentralization: > http://web.mit.edu/ghudson/thoughts/bitkeeper.whynot wich one for us ? I think for docutils we are more in the situation of : =AB Although a changeset-oriented source control tool is useful in many contexts (offline development on a laptop and private branches of a project, to name two) =BB I see two main problem with centralized system : - need to find a server, and depend of the this server (is it online when you need to commit ? and are we online also ?) - need to give write access to all the developers. I've no experience with big centralized development, but for my own litle projects, it help me a lot after CVS. Even when you work alone on a project, the branching system and the possibility to commit on a laptop is very good and very easy to install and use. But anyway, you can also use arch in a centralized manner, like i show with the example of a sprint. (the shared file-system could be online of course) > > Also, Subversion is very easy to learn if you know CVS. On one part, subversion is maybe easy to learn, but it's not easy to find a server, and impossible on sourceforge now... On second part, we don't change a version control system every day ! So it's a good time to learn, why do you want to learn it quickly ? Specialy you ;-) --=20 William Dode - http://flibuste.net |