QA 過程 for Localized Builds
This 過程 is in 進歩, and as better 過程s become 明らかな, we will follow them and change this 指導基準. The 実験（する）ing of the builds 深く，強烈に 伴う／関わるs the QA and Native-Lang 事業／計画（する）s. Notices pointing to this 過程 指導基準 will be 地位，任命するd on those 事業／計画（する）s and also on the l10n 事業／計画（する）.
Where do the localizations come from?
Localized builds are created by the community. The l10n 事業／計画（する） 調整するs this activity, and one can 見解（をとる） the status of any 現在進行中の localization by checking the status page.
What do we do here, in QA?
The point of having QA 実験（する） these builds is to 減ずる the 可能性 that the builds won't work. They may still be rough, but by going through the QA 過程, we can at least 確実にする that we won't be sending out to the world builds that can't be 任命する／導入するd, won't work at all, ...
What is the QA 過程?
- Localized builds are made
利用できる at several places. These are:
- the mirror 網状組織 under the /contrib/rc directory for most of the builds 供給するd by hamburg 解放（する） 工学.
- http://oootranslation.services.openoffice.org/pub/OpenOffice.org/ for language packs or 十分な builds 供給するd by hamburg 解放（する） 工学.
- places used by contributors for different 壇・綱領・公約 builds.
- The builds are 登録（する）d and managed in OpenOffice.org QATrack.
The builds are submitted by the QA 事業／計画（する）, and updated by each build's responsible to 示す the
build's 現在の status. Often the responsible is one of the qa responsibles in the Native Lang community.
For more （警察などへの）密告，告訴（状） about OpenOffice.org QATrack, see the system's Help section.
There might be a slight 延期する for the submission of some builds. Therefore, for most 現在の （警察などへの）密告，告訴（状） about the availability of these builds you should subscribe to the 関連した mailing 名簿（に載せる）／表（にあげる）s:- 解放（する）s@openoffice.org
- dev@porting.openoffice.org
- Native-Lang leads or their 委任する／代表s 割り当てるd to the 仕事 of helping QA the builds download the builds and run through a 一連の 実験（する）s. This 過程 should begin すぐに upon the availability of localized 解放（する） 候補者s and should not take more than two weeks from beginning to end. For managing those testcases, 実験（する） assignemnts and results we use the TCM (実験（する） 事例／患者 管理／経営) Portal
- An IssueTracker ticket should
be とじ込み／提出するd so as to move the 実験（する）d
builds over to the /localized directory for proper 石油精製
dissemination and to update the pages. Mirrors need to be 通知するd by
the 配当 事業／計画（する） lead.
This should be とじ込み／提出するd as "仕事" for 構成要素 "qa", subcomponent "www". 割り当てる it to the default owner and make shure, you 指名する the exact 場所 of the とじ込み／提出するs that have been used for 実験（する）ing. - Finally, once the mirror 網状組織 has 示すd that the builds have been 首尾よく uploaded into the proper directory, the builds may be 発表するd by the appropriate persons, such as the Native-Lang leads and Community 経営者／支配人.
$Revision: 1.17 $
