+1. Git and many others all have their valid point but
- none is mainstream enough (we're already striving for getting people
to participate in Magnolia, there are enough (ie too many) entry
barriers as it stands)
- subversion is still evolving and the latest version (1.5) addresses
some of the branching issues - it'd probably be a better (and smaller)
investment to see if that would bring us any benefit.
- there's a new-hot-thing in scm every other month, so i'd rather wait
and see what happens until we actually have a real issue with svn (to
Boris: yeah, the issue I had yesterday --- my local copy was
corrupted, that's all :p)
-g
On Oct 30, 2008, at 9:58 AM, Philipp Bracher wrote:
Looks tempting. Having temporal branches outside the main repository
has definitely its point. The obstacle I can see is all the effort
which would have to be done. And therefore I am not sure if it paid
off.
- jira integration
- IDE integration (collaborate with maven plugins)
- migration of current svn content
- ..
Since I don't feel as if I miss something in subversion today I
don't like to move in the next months.
Philipp Bracher
----------------------------------------------------------------
for list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
----------------------------------------------------------------
