OpenOffice.org source 支配（する）／統制する
OpenOffice.org main codelines
OpenOffice.org does use the cvs Source 支配（する）／統制する System. The major 解放（する）s of OpenOffice.org are 器具／実施するd on, so called, cvs 支店s. The 開発 of the next major 解放（する）s is developed on HEAD of the cvs tree, the 維持／整備 of older 見解／翻訳／版s also happens on 支店s.
In
the OpenOffice.org 環境 these 支店s are often called
codelines or master(-支店s). Builds on these codelines does not
happen continuously (daily builds) but within 正規の／正選手 milestones. For
the 1.1.x codeline this result in a cvs 支店 tag called mws_srx645
which 代表するs the 最新の status of this codeline and several more
tags which 代表する a 明確な／細部 milestone on this codeline
(SRX645_m34, SRX645_m40). The same 計画／陰謀 適用するs to the 2.0 codeline
(mws_src680 for the 最新の status, SRC680_m36 for a 明確な／細部
milestone). Usually every week there will be a new milestone on the
active 開発 line 利用できる. There is also the 可能性 to
達成する some more granularity with the introduction of steps, so that
more than one build per week is possible (SRC680_m33s1).
The 指名するs like SRC680, SRX645 will be deprecated in the 未来, they 代表する the old 計画／陰謀 of milestone 指名するing.
As soon as the OOo 2.0 comes の近くに to 解放（する）, a new 支店 for this codeline will be created so that concurrent 開発 of the next 解放（する） can be started.
開発 支店s
Since OpenOffice.org build times are pretty high and the goal is to have at all times a milestone 利用できる which is in 解放（する） 質, no commits to the master codeline are made. OpenOffice.org is developed by more than 100 developers, it builds for more than 10 壇・綱領・公約s, for more than 25 languages and it has more than 7 million lines of code with a plenty of build time needed for a 完全にする recompile. So the 危険 of breaking something is pretty high, even if the comitters is sure about his changes. 予定 to this 複雑さ we introduced the 概念 of doing any feature 開発 and bug 直す／買収する，八百長をするs on cvs 支店s. This means that a new feature has to be developed on a cvs 支店, until the feature is 完全にする and has been 実験（する）d on at least to major 壇・綱領・公約s (usually one Unix derivate and Windows). The same 適用するs for bugs 直す／買収する，八百長をするs, but bug 直す／買収する，八百長をするs should be grouped together on one 支店.
These
支店s are called within the OpenOffice.org 環境 child
workspaces. Since it is possible to create many child workspaces
in 平行の, some 付加 過程s has been developed to make
life more 平易な and 安全な・保証する on these child workspaces. For example, the
problem of “repeated 合併するs” is やめる ありふれた in cvs. This
状況／情勢 occurs やめる often when 取引，協定ing with many 支店s in
平行の, for example if a bug 直す／買収する，八百長をする has been 適用するd to more than one 支店.
Child workspace resynchronization
Many of the “repeated 合併する” problems can be solved before the 合併する 支援する to the master 支店 if you were able to bring your copy of the cvs 支店 up to date of the 最新の know stable 見解／翻訳／版 of your master. For this the resynchronization 活動／戦闘 (cwsresync) 命令（する） has been introduced.
The
resync 機械装置 is able to を取り引きする repeated 操作／手術, so that
this 過程 can be 遂行する／発効させるd frequently. In 事例／患者 a 衝突 has to be
解決するd, this will happen in the child workspace, so the 危険 of
having a broken master workspace is いっそう少なく than in the classical
approach, when a 支店 will be 合併するd 支援する to the master with the
usual 'cvs update' 命令（する）.
Child workspace reintegration
When all the changes 存在 made on a child workspace are joined 支援する, the スピードを出す／記録につける history of the 支店 will be saved and 蓄える／店d in the スピードを出す／記録につける history of the trunk 同様に. さもなければ the 跡をつけるing of what had happened on a 支店 is difficult.
Since the reintegration is always done by a unique （独立の）存在 (usually 解放（する） 工学 associated with this codeline) we loose the ability to see the 初めの author of a 選び出す／独身 line with the 'cvs annotate' 命令（する）, but we still are able to see when a line of code has been changed and can use the スピードを出す／記録につける for getting more 詳細（に述べる）s.
改正 1.38
date: 2004/04/02 13:49:24; author: rt; 明言する／公表する: Exp; lines: +9 -1
INTEGRATION: CWS sj05 (1.34.80); FILE MERGED
2004/03/15 13:47:50 sj 1.34.80.4: RESYNC: (1.36-1.37); FILE MERGED
2004/02/13 17:38:38 sj 1.34.80.3: RESYNC: (1.34-1.36); FILE MERGED
2004/02/09 15:01:36 cl 1.34.80.2: #i20484# 追加するd new CustomShape ui
2004/02/04 11:39:15 cl 1.34.80.1: #i20484# 追加するd new CustomShape ui
----------------------------
改正 1.37
date: 2004/02/25 15:55:41; author: kz; 明言する／公表する: Exp; lines: +0 -10
INTEGRATION: CWS layoutmanager (1.34.20); FILE MERGED
2004/02/19 16:33:04 cd 1.34.20.3: RESYNC: (1.35-1.36); FILE MERGED
2004/01/29 16:56:22 cd 1.34.20.2: RESYNC: (1.34-1.35); FILE MERGED
2003/11/24 07:25:16 cd 1.34.20.1: #111899# 除去する old menu 監査役 登録
----------------------------
改正 1.36
date: 2004/02/03 16:35:11; author: hr; 明言する／公表する: Exp; lines: +17 -12
INTEGRATION: CWS dialogdiet (1.34.60); FILE MERGED
2004/01/26 14:32:05 mba 1.34.60.3: #i22972#: SvxErrorHandler needs to be created by apps
2004/01/19 23:47:01 mba 1.34.60.2: RESYNC: (1.34-1.35); FILE MERGED
2003/11/28 18:08:12 mba 1.34.60.1: #i22972#: offmgr 除去するd
環境 （警察などへの）密告，告訴（状） System (EIS)
There is a web frontend to 見解（をとる） a 名簿（に載せる）／表（にあげる） of child workspaces and their status ( http://eis.services.openoffice.org/EIS2/servlet/GuestLogon). The status of a child workspace and the corresponding master workspace can be 見解（をとる）d.
