Hi Guido, Guido Ostkamp wrote: > Hello, > > On Mon, 9 Jun 2008, Jens-Heiner Rechtien wrote: >> As some of you might know, the OOo engineering steering committee >> (http://wiki.services.openoffice.org/wiki/ESC_minutes#SCM_review) >> decided that OOo will migrate to Subversion first but to reevaluate >> the big three DSCM systems (Bazaar, Mercurial and Git) within a year >> to account for new developments. > > well, when reading this I've mixed feelings. While branching with > Subversion might be a lot easier compared to CVS, it still requires > server access which free developers might not have. OTOH Subversion > supports checking out partial trees.
Free developers without Internet access? ... Well, maybe not all the time, right. :) > > I think there are conversion tools from Subversion to Git, Mercurial and > Bazaar that allow to keep a DSCM repo in sync with a Subversion master > repository at least one-way. > > I don't know how expensive this would be, but would it be possible to > maintain a Git clone as a mirror that is synced with the Subversion repo > on at least daily basis? I haven't looked into this conversion tools closely yet. If it's possible in a reasonable way I pretty sure we can and will offer something like that. Both systems are changeset based, Subversion keeps a bit more internal state than git, so yes, this could work. > > This would at least allow people to get the best of both worlds. Changes > would of course have to be committed to Subversion. > >> <...>/cws <= place for CWSs > > Are you really going to migrate all old CWS that ever existed in CVS or > are you skipping stuff that has been migrated to real versions? No, all integrated, closed or deleted CWS will be left out from the conversion. Saves us some 5000 branches :) > > Will the subversion repo cover just OOo 3.x or older versions as well? Older as well. Actually trunk and all releases should be covered. Will be a huge repository ... Heiner --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
