Switching from CVS to Subversion: test svn repo available

[Fabien COELHO]

Dear Chris,

> ** Changesets **
> ** Centralized vs. Distributed **
>        In summary, I think there are two main reasons for looking
> further than SVN for SCM software.  1) Changesets are a big
> convenience for all developers.  2) Distributed SCM lets fringe
> developers benefit from a real SCM, too.

I must first state that I'm biased towards SVN. Nevertheless:

The actual question you should ask is "what is a desirable development
model for gnucash", and then chose the best tool to support that model.
Best is about features / support / stability / easy to understand / 
free / available / portable...

If you're in a war zone with many developpers where everybody wants to 
develop its "own" personnal version and no one can fully agree on 
something common (say you're in the linux kernel;-) then changesets and a 
distributed approach is the (only) way to handle the anarchy;-)

If you want to produce "one" stable software with a close collaboration 
between (few) developers, then the centralized solution looks much better 
to keep control of what is going on. I agree that changesets are better 
than simple file histories, but svn provides a reasonnable approximation. 
ISTM that subversion's 'fsfs' backend does store changesets internally, by 
the way.

So I think that svn as a better cvs is a good move for *gnucash*, although 
it may not necessarily be the case for other softwares with different 
aims and cultures.

-- 
Fabien COELHO   _____   fabien at coelho.net   _____   http://www.coelho.net