Revision as of 17:07, 22 August 2008 (view source) Hr (Talk | contribs) ← Older edit		Revision as of 17:19, 22 August 2008 (view source) Hr (Talk | contribs) Newer edit →
Line 20:		Line 20:
	==Required tools==		==Required tools==
		+
		+	* subversion-1.5.1 or later
		+	* ssh for committers, preferably OpenSSH 2.4 or later
		+
		+	We make heavy use of the new SVN merge tracking feature. So please do not use a SVN client older than subversion-1.5.1
	==Server, access methods==		==Server, access methods==
		+
		+	===Read only access===
		+
		+	<code>
		+	svn co svn://svn.services.openoffice.org/ooo/trunk
		+	</code>
		+
		+	or
		+
		+	<code>
		+	svn co http://svn.services.openoffice.org/ooo/trunk
		+	</code>
		+
		+	===Read/write access===
		+
		+	Write access to the repository requires a ssh setup.
		+
		+	<code>
		+	svn co svn+ssh://svn@svn.services.openoffice.org/ooo/trunk
		+	</code>
		+
	==Ssh setup==		==Ssh setup==

---

Revision as of 17:19, 22 August 2008

OpenOffice.org migrates to Subversion

After a long discussion and preparation time it finally happens, OpenOffice.org migrates with milestone DEV300 mxx to a new SCM (Software Configuration Management) system. The new SCM system will be Subversion (SVN) for now, which might disappoint the one or other who has hoped for a distributed SCM like Git, Bazaar or Mercurial. Please be assured that we'll keep our mind open and we'll reevaluate the fast moving SCM tooling situation periodically. We were very careful to make certain that our move now to Subversion does not preclude a move to a DSCM in the future.

Trunk only migration

Milestone DEV300 mxx is the last milestone which has been integrated via CVS and is the first milestone which is available in SVN. We did a trunk migration only. The trunk (DEV300) code line will be maintained via Subversion only starting with milestone DEV300 mxx+1. Old code lines, including the OOo-3.0 release codeline(OOO300) will still be maintained via CVS.

Please let me repeat this: we did not migrate branches and tags to SVN. There are a number of advantages (and some disadvantages as well) to this approach. A discussion of the merits of different approaches to the actual repository conversion can be found here.

The most important reasons for choosing the "trunk only" approach were:

• No quiet time for developers
• The conversion of historical workspaces from CVS to SVN would be fragile at best due to some liberties we took in structuring our CVS repository. Having no historical branches and tags is preferable to having inaccurate branches and tags IMHO.

The "trunk only" approach enabled us to optimize the resulting SVN repository, it shrunk from 90 GBytes to about 6 GBytes overall size. The following rules have been applied during conversion

• Only modules which have active content in DEV300 mxx are included in the conversion.
• All files in "Attic" have been removed.
• All but the last revisions of binary files have been dropped - after all you can't diff them anyway
• All but the last revisions of "localize.sdf" files have been dropped - saves an incredible amount of repository space without loosing much

Required tools

• subversion-1.5.1 or later
• ssh for committers, preferably OpenSSH 2.4 or later

We make heavy use of the new SVN merge tracking feature. So please do not use a SVN client older than subversion-1.5.1

Server, access methods

Read only access

svn co svn://svn.services.openoffice.org/ooo/trunk

or

svn co http://svn.services.openoffice.org/ooo/trunk

Read/write access

Write access to the repository requires a ssh setup.

svn co svn+ssh://svn@svn.services.openoffice.org/ooo/trunk

Ssh setup

CWS tooling

Tips and tricks

Notes

why