OpenOffice.org migrating to Mercurial
The OpenOffice.org (OOo) project has announced that it will be switching to Mercurial as its source code management (SCM) tool for the future development of its open source office suite. The project developers chose Mercurial over other distributed source code management tools, such as Git or Bazaar, because they "believe that its combination of ease of use, flexibility and performance fits best with the overall OOo needs".
According to the announcement, the DEV300 development code will switch to Mercurial first, followed by the OpenOffice.org 3.2 release code (OOO320). The initial change will occur "around the 26th of October". The developers advise that various announcements regarding the change, such as where to find the latest documentation and the last SVN based milestone, will be made to the OOo mailing lists over the next two weeks.
See also:
- OpenOffice 3.1.1 fixes bugs, a report from The H.
(crve)
![Kernel Log: Coming in 3.10 (Part 3) [--] Infrastructure](/imgs/43/1/0/4/2/6/7/2/comingin310_4_kicker-4977194bfb0de0d7.png)
![Kernel Log: Coming in 3.10 (Part 3) [--] Infrastructure](/imgs/43/1/0/4/2/3/2/3/comingin310_3_kicker-151cd7b9e9660f05.png)
