[M3devel] SVN migration

[Dragiša Durić]

Saw. Read.

SVN is sort of mature, finished CVS. I am 100% sure I don't have your
SCM experience, but if SVN's only advantage was trac integration I think
it would be more than enough reason to move to it.

Trac's got wiki for documentation, very granular access control, nice
hyperlinking mechanism for changesets-wiki-tickets-... Whoever gets a
bit of free time and inspiration, with trac he can contribute to cm3 in
some way. We definitely can have better flow of information with it.

I don't know much what you mean under "existing infrastructure".
Building/testing insfrastructure? Access to CVS repo? 

dd

On Sat, 2008-03-15 at 19:03 +0100, Olaf Wagner wrote:
> Quoting Dragiša Durić <dragisha at m3w.org>:
> 
> > Why don't we migrate to SVN?
> >
> > It's piece of cake to convert CVS repo, and IIRC it can be done
> > incrementally.
> 
> See https://mail.elegosoft.com/pipermail/m3devel/2008-January/000803.html
> and https://mail.elegosoft.com/pipermail/m3devel/2008-January/000855.html
> 
> > What I think would be real benefit is trac - we can do
> > some real cooperation and documenting using it.
> 
> There already is a trac installation on www.elegosoft.com to
> which some old PRs from our GNATs system have been copied. It's
> not really integrated to CVS and tinderbox yet; I haven't had time
> to really test it since our system administrator set it up. So
> there's still some work to do.
> 
> I'll talk to Ronny on monday if we can open trac write access
> for all M3 users.
> 
> It's at https://bugs.elego.de/cm3/.
> 
> > CVSup is real nice tool, but whoever needs local repo can have it using
> > rsync. I don't think it would make big oberhead anywhere, not these days
> > and this hardware/bandwidth we usually have today.
> 
> But it would break existing infrastructure. I for one haven't got time
> to spent on setting up something different again.
> 
> Olaf
-- 
Dragiša Durić <dragisha at m3w.org>