[Kolab-devel] Switch to hg timeline (Re: Poll: Kolab server switching to Mercurial SCM?)
Bernhard Reiter
bernhard at intevation.de
Tue Apr 13 11:05:18 CEST 2010
Am Montag, 12. April 2010 07:07:31 schrieb Gunnar Wrobel:
> Quoting Thomas Arendsen Hein <thomas at intevation.de>:
> > The original plan was to wait for an upgrade of wald.intevation.org
> > to a current FusionForge version, but maybe I'll start earlier with
> > a repository on hg.intevation.org. Having two repositories who sync
> > with each other is absolutely no problem as soon as Wald grows
> > support for Mercurial trees.
IMO we could also have the repository on wald which have been manually
initialisied.
> > So maybe within two months?
>
> Thanks for the feedback. I personally hope for ASAP ;)
I also would have first a sooner start of the migration period.
> as I'd really
> like to have the additional flexibility of mercurial as compared to
> CVS. I'd like to start playing around with a different way of
> packaging (project-builder) and as that involves new directories
> and/or a different structure - again ;) - I'm tempted to wait for hg
> there. I can probably play around on github in the meantime though.
Playing with hg.intevation.org should not be a problem.
--
Managing Director - Owner: www.intevation.net (Free Software Company)
Deputy Coordinator Germany: fsfe.org. Board member: www.kolabsys.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/devel/attachments/20100413/f155b113/attachment.sig>
More information about the devel
mailing list