State of the OOo SCM project ============================
As some of you might know, the OOo engineering steering committee (http://wiki.services.openoffice.org/wiki/ESC_minutes#SCM_review) decided that OOo will migrate to Subversion first but to reevaluate the big three DSCM systems (Bazaar, Mercurial and Git) within a year to account for new developments.
We plan to switch over to Subversion in the second half of July. A server with sufficient computing power and network bandwidth has been specified and will be available until the end if June. This is nice, because we'll have time to test the configuration thoroughly.
We plan to use Subversion 1.5 (which is currently in RC9), because it makes scripting so much easier due to merge tracking - actually it eliminates scripting requirements for rebasing and integration. Well, merge tracking is quite new so should there be any problems with that we'll fall back to Subversion 1.4.6.
The tentative structure of the repository is as follows: <...>/trunk <= HEAD <...>/tags <= milestones and release tags <...>/branches <= DEV300, DEV301 etc, development branches <...>/cws <= place for CWSs <...>/vendor/x <= space for vendor specific trees <...>/vendor/y (customization, patches whatever) <...>/contrib/ <= space for experimental trees, ind. developers Suggestions etc are welcome! Heiner -- Jens-Heiner Rechtien [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
