Wednesday, 14 Oct 2009
Wednesday, 14 Oct 2009
I'm very pleased to announce, that after five months of piloting,
implementation and and testing, we are finally ready to switch
OpenOffice.org development to Mercurial (hg) as our SCM (Source Code
Management) tool.
Mercurial is a modern and flexible distributed SCM tool with the fast
and convenient merging capability which is so required for OOo development.
We have chosen Mercurial out of the three major open source DSCM tools
available (Git, Bazaar and Mercurial) because we believe that its
combination of ease of use, flexibility and performance fits best with
the overall OOo needs. We are well aware that a slightly different
emphasis on the selection criteria might well have led to a choice of
Git or Bazaar, which are both very capable DSCMs as well.
Details:
We'll switch the DEV300 development code line first, the OOO320
(OpenOffice.org 3.2 release code line) will follow later. We certainly
don't want to interfere with the OOo 3.2 release.
The DEV300 switch will happen around the 26th of October. The current
DEV300 hg mirror repository on hg.services.openoffice.org will be
elevated to be the reference repository, which is the place where release engineering pushes
released milestones. Simultaneously release engineering will stop to
commit new milestones to the current Subversion (svn) trunk.
Please stay tuned!
During the course of the next two weeks I'll make some
announcements on the OOo mailing lists regarding the switch to Mercurial:
- where to find documentation
- which will be the last svn based milestone
- conversion of child workspaces to hg
- conventions which we will use
I'll give a talk at the OOo conference 2009 in Orvieto. If you happen to be there, this is just the right opportunity to throw ripe tomatoes at me ask me in person about the background of this migration, why we haven chosen Mercurial over Git or Bazaar and what our future plans are. Hope to see you there!
tags: hg mercurial ooo openoffice.org
Comments
Is it possible to download a bundle file of a snapshot of 'http://hg.services.openoffice.org/DEV300/' and then hg pull/hg up?
Posted by Hussam Al-Tayeb on October 14, 2009 at 06:24 PM CEST #
@Hussam Al-Tayeb: it's not yet possible to download a bundle file, but this is a very good suggestion. I'll check if it's possible to always provide a bundle of the latest milestone to ease the first download.
Posted by Jens-Heiner Rechtien on October 14, 2009 at 07:31 PM CEST #
@Hussam Al-Tayeb: A nightly (GMT) generated bundle file of the tip of 'http://hg.services.openoffice.org/DEV300" is now available as 'http://hg.services.openoffice.org/bundle/DEV300.hg". The bundle has currently a size of about 800 MB.
Posted by Jens-Heiner.Rechtien on October 15, 2009 at 03:49 PM CEST #
Great, thank you very much :)
Posted by Hussam Al-Tayeb on October 15, 2009 at 03:53 PM CEST #
If you are keeping binaries in your repo, you will be very unhappy in a year or so: the repo will grow, and grow, and grow... and doing a new clone will be impractical. Consider: http://wiki.netbeans.org/ExternalBinaries
Posted by Jesse Glick on October 22, 2009 at 04:07 PM CEST #
@Jesse: We do currently keep some external binaries in the repository, and they do have a very noticeable effect, unfortunately. Our plan is to use a mechanism very much like the Netbeans one, it will be one of the first things we'll implement after the switch. In the meantime I'm going to scrutinize the necessity of each commit over a certain size.
Posted by Jens-Heiner Rechtien on October 22, 2009 at 08:02 PM CEST #
Vallaha siteniz çok güzel backlink veriyo allah razı olsun sizden
http://www.yerindeegitim.com
http://www.internetce.net
http://www.partneriniz.net
http://www.bayaneskort.tk
http://www.askkervani.com
Posted by web tasarımı internet sitesi on October 28, 2009 at 09:24 PM CET #