Mercurial-Implementation: OOo domain developer public keys

Hi OOo Mercurial users,

OOo domain developers public keys
=================================

The SVN public keys of all OOo domain developers can now be used to r/w
access the "outgoing" mercurial repositories on
hg.services.openoffice.org via SSH
(ssh://[email protected]/cws/*).

It's no longer necessary to be part of the Mercurial Pilot (which has
been concluded weeks ago anyway) or to contact RE if you want to try out
a Mercurial based CWS.

There are still some caveats with Mercurial based child workspaces as
long as we still use SVN for tracking our code lines:

*  Your changesets will loose their identity during integration. This
might create problems if you cross merged changesets between several CWSs.

* Integration into SVN will lump all changeset of your CWS into one
single changeset. The single changeset commit during integration will
contain of course only a single commit log. We lump together all commit
logs and authors of your changesets together via scripting and attach
that to the commit. Alternatively REs will accept a detailed commit log
supplied by you. The

* Be careful with renaming files. If you do a lot of renaming you'll
most probable cause a lot of stress on the integrator. Remember, the RE
integrate your CWS via diff and patch. Also, all restrictions of SVN
regarding the renaming of files/directories still apply. If you plan to
do a lot of renaming please do it on a SVN based repository. Or better,
if possible, wait for the final switch to hg.

* Tinderboxes, buildbots etc are currently adapted to Mercurial, some
things might not yet work.

Please contact me if you have problems, suggestions etc.

Regards,
   Heiner