Hi OOo Mercurial users,

Automatic creation of "outgoing" repositories
=============================================

The mechanism for the server side creation of the "outgoing" CWS
repositories on hg.services.openoffice.org is in now place.

An outgoing repository is automatically created for every CWS which is:
a) flagged for Mercurial use
b) in state "new" or later (but not for "planned")

It's no longer necessary to request Mercurial based CWSs per email.

Any newly created mercurial based CWS should appear in this list no
later than about two hours after the creation of the CWS:
http://hg.services.openoffice.org/hg

Fresh "outgoing" repositories will contain every milestone up to the
creation milestone of the CWS, this ensures minimal network transfers
consistent with the prevention of unnecessary heads.

If the "outgoing" respository for your CWS is not properly created
please notify me.

Flag your CWS as mercurial (hg) based
=====================================

It's possible to flag your CWS as hg based by editing the SCM entry in EIS.

Starting with DEV300 m57 "cws create" accepts a new option "--hg":

$ cws create --hg DEV300 <cwsname>

This will create a CWS with name <cwsname> in EIS with is by default
flagged for Mercurial usage. Also it doesn't create these superfluous
branches in SVN anymore.

Please don't use this switch for OOO310 childworkspaces.

Setting the current milestone of a CWS
======================================

Starting with DEV300 m57 the "cws" tool knows a new command:

$ cws setcurrent -m <milestone>

Use this to set the correct current milestone in EIS. You'll need this
for hg based child workspaces because there is no wrapper (yet) to do
this after a pull/merge. I'm currently thinking about how to set the
current milestone automatically, but nothing is in place yet.

You can set the master code line with this command as well, please use
this prudently.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org

Reply via email to