Difference between revisions of "Mercurial/Cws"
m (→Other Mercurial Topics) |
|||
| Line 1: | Line 1: | ||
| + | This page discusses the Mercurial part of handling child workspaces (CWSs). It assumes some basic Mercurial knowledge which you can find [[OOo and Mercurial|here]]. | ||
| + | |||
= Other Mercurial Topics = | = Other Mercurial Topics = | ||
* [[Setting up Mercurial]] | * [[Setting up Mercurial]] | ||
| Line 5: | Line 7: | ||
* [[MercurialTipsAndTricks | Tips and Tricks]] | * [[MercurialTipsAndTricks | Tips and Tricks]] | ||
| − | = Mercurial and | + | = The OpenOffice.org setup = |
| + | |||
| + | The OpenOffice.org Mercurial repository is huge, it contains more than 260000 changesets and exceeds 1 GiB in size. Repeatably exchanging this vast numbers of changesets over the Net is prohibitive and wasteful. It's also not necessary. We were careful to employ a setup which is designed to minimize the number of changesets exchanged over the Net. The basic idea is to create a so called 'outgoing' repository for each CWS on the main OOo SCM server. The 'outgoing' repository already have each changeset up to and including the milestone the CWS was created on. The 'outgoing' repository is meant as the main collaboration tool around the child workspace and is also the place where release engineering will fetch a child workspace when it's ready for integration. | ||
Revision as of 19:54, 25 October 2009
This page discusses the Mercurial part of handling child workspaces (CWSs). It assumes some basic Mercurial knowledge which you can find here.
Other Mercurial Topics
- Setting up Mercurial
- Migrating existing CVS or SVN based child workspaces to Mercurial
- Using Mercurial with OpenOffice.org: getting started
- Tips and Tricks
The OpenOffice.org setup
The OpenOffice.org Mercurial repository is huge, it contains more than 260000 changesets and exceeds 1 GiB in size. Repeatably exchanging this vast numbers of changesets over the Net is prohibitive and wasteful. It's also not necessary. We were careful to employ a setup which is designed to minimize the number of changesets exchanged over the Net. The basic idea is to create a so called 'outgoing' repository for each CWS on the main OOo SCM server. The 'outgoing' repository already have each changeset up to and including the milestone the CWS was created on. The 'outgoing' repository is meant as the main collaboration tool around the child workspace and is also the place where release engineering will fetch a child workspace when it's ready for integration.
