Hi,
I saw the discussion of the hostname in the comments.
Do we want to go ahead with hg.services.openoffice.org or use something
more general like source.s.ooo or src.s.ooo?
Let's nail this down right from the beginning so that the svn.s.ooo
isn't abused ;-)
Greetings
Stefan
Jens-Heiner Rechtien wrote:
Hi,
I've been working on another project lately, but since this one is
nearing finalization I'll have the time for the preparation of the
Mercurial pilot RSN now. I'll announce the details here on the list.
Some more details here:
http://blogs.sun.com/GullFOSS/entry/mercurial_pilot_for_openoffice_org
Heiner
Martin Hollmichel wrote:
Hi *,
The ESC meeting agreed more than a year ago to migrate OpenOffice.org's
version control from CVS via subversion towards an distributed source
code managment (DSCM) system. The ESC is also in agreement that right
now git and mercurial are both systems which are able to fulfil the
requirements we have but there is no vast majority towards one of the
systems. This is no real surprise since also other projects still don't
show a clear favorite. The ESC also is in agreement that we should
migrate now or in the very near future we can not afford to wait which
system will win the race. Since the release engineering team is in favor
of mercurial I ask - as the tools project lead - the RE team to start
the pilot for mercurial now so that we will be able to have the new DSCM
available with the 3.2 release.
This is not an easy decision. But we had the choice, this was possible
by the availability of the free, open source projects bzr, git and
mercurial. Thanks to them and the teams that worked on the evaluation
for an migration to OpenOffice.org.
This is not a decision against one of them because of technical
concerns, it is a pragmatic decision,
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
