Difference between revisions of "JA/QA/Release/template en"

From Apache OpenOffice Wiki
< JA‎ | QA
Jump to: navigation, search
(2.4.2のリリースストッパーのIssue)
(参考リンク)
 
(11 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
==About QA and release==
 
==About QA and release==
  
Each native language projects are correspondence and responsible for release.
 
 
To release your native language version of OpenOffice.org,  
 
To release your native language version of OpenOffice.org,  
 
each language project proceeds QA (quality assurance).
 
each language project proceeds QA (quality assurance).
 +
Each native language projects are correspondence and responsible for the release.
  
The Japanese language project is responsible for Japanese version of OpenOffice.org.
+
For example, the Japanese language project is responsible for Japanese version of OpenOffice.org.
Each language, for example German, French etc., project will
+
do it of each language.
+
  
 
References
 
References
Line 14: Line 12:
  
 
==Primary information about release candidates and release status==
 
==Primary information about release candidates and release status==
You can obtain information about uploaded release candidates and their status at
+
You can obtain information about availability release candidates and their status at
 
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes Release status minites]
 
[http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes Release status minites]
 
and  
 
and  
Line 20: Line 18:
 
.
 
.
  
==[http://qatrack.services.openoffice.org/ Release QA status of packagesQATrack]==
+
==[http://qatrack.services.openoffice.org/ Release QA status of build : QATrack]==
  
Login to QATrack required. Username and password are the same as when you login to OpenOffice.org site.
+
The QATrack has all information for QA of your language; e.g., in QA, build has been approved, and distributed.
  
 
*[http://qatrack.services.openoffice.org/ QATrack]
 
*[http://qatrack.services.openoffice.org/ QATrack]
 
*[http://qatrack.services.openoffice.org/view_status.php?version=2.4.2&language%5B%5D=ja&available=&uri=&view=overview 2.4.2 JA build status]
 
*[http://qatrack.services.openoffice.org/view_status.php?version=2.4.2&language%5B%5D=ja&available=&uri=&view=overview 2.4.2 JA build status]
  
QA track has all information for QA of your language; in QA, QA has been finished, and distributed.
+
Login to QATrack required. Username and password are the same as when you login to OpenOffice.org site.
  
 
==[[OOoRelease242|Release schedule of US English version of 2.4.2]]==
 
==[[OOoRelease242|Release schedule of US English version of 2.4.2]]==
Line 58: Line 56:
 
* http://wiki.services.openoffice.org/wiki/OOoRelease242
 
* http://wiki.services.openoffice.org/wiki/OOoRelease242
  
==2.4.2用VCL TestToolのダウンロード==
+
==VCL TestTool for 2.4.2==
 
[http://qa.openoffice.org/ooQAReloaded/AutomationTeamsite/ooQA-TeamAutomationBin.html VCL TestTool Binaries OOo 2.4 / OOo 3.x]
 
[http://qa.openoffice.org/ooQAReloaded/AutomationTeamsite/ooQA-TeamAutomationBin.html VCL TestTool Binaries OOo 2.4 / OOo 3.x]
VCL TestToolのバイナリはかならずここからとってください。
+
Please download VCL TestTool binary from the link above.
  
* [http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=9992 アナウンス]
+
* [http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=9992 Announcement]
 
* [http://wiki.services.openoffice.org/wiki/VCLTesttool_2.4 VCLTestTool 2.4]
 
* [http://wiki.services.openoffice.org/wiki/VCLTesttool_2.4 VCLTestTool 2.4]
 
* [http://blogs.sun.com/GullFOSS/entry/make_results_of_automated_tests autmated tests]
 
* [http://blogs.sun.com/GullFOSS/entry/make_results_of_automated_tests autmated tests]
  
==2.4.2用VCL TestTool環境のダウンロード==
+
==VCL TestTool environment for 2.4.2==
[ftp://ftp.ooodev.org/pub/qa/qatesttool_ooo240.tgz OOo 2.4.2用 VCLTestTool環境]
+
[ftp://ftp.ooodev.org/pub/qa/qatesttool_ooo240.tgz OOo 2.4.2用 VCLTestTool Environment]
  
[ftp://ftp.ooodev.org/pub/qa/qatesttool_ooo240.tgz.md5 VCLTestTool環境のMD5SUM]
+
[ftp://ftp.ooodev.org/pub/qa/qatesttool_ooo240.tgz.md5 MD5SUM of the VCLTestTool environment]
  
これは、Andre Schnabelによるチェックアウトです。
+
This a checkout by Andre Schnabel.
  
典拠
+
References
 
# [http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=10550 about tag: For Builds >= DEV300m14 use HEAD]
 
# [http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=10550 about tag: For Builds >= DEV300m14 use HEAD]
# [http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=9262 一日おきにアップデートする旨 Andre Schnabel]
+
# [http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=9262 Update every day by Andre Schnabel]
# [http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=9185 アナウンス by Andre Schnabel]
+
# [http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=9185 Announcement by Andre Schnabel]
# [http://wiki.services.openoffice.org/wiki/Cvs_tags_and_branches CVS tag and branches(VCLTestTool環境をどうやってチェックアウトするか)]
+
# [http://wiki.services.openoffice.org/wiki/Cvs_tags_and_branches CVS tag and branches(How we can checkout VCLTestTool environment)]
  
==2.4.2のテスト方法とリリース許可の判断==
+
==How you test 2.4.2 release candidates and how release candidates get approved==
  
テスト方法は以下の三通り
+
We JA project define the following three tests for approval of the release candidates
* [http://ja.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=17063 TCMテストによるSanityテスト]
+
* [http://ja.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=17063 Sanity TCM test (in Japanese)]
* [http://ja.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=16407 VCLTestToolによるSanityテスト]
+
* [http://ja.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=16407 Sanity test by VCLTestTool (in Japanese)]
* [http://ja.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=16410 簡単なリリーステスト]
+
* [http://ja.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=16410 Sanity test (in Japanese)]
  
リリース許可の判断
+
Release criterion
  
* 1パッケージあたり少なくとも1つの環境で、上記の一つ以上の方法でテストされていること。
+
* One release candidate must be tested at least one of the method described above.
* 全てのテストが通らなくてもいいが大体通っていること。
+
* Almost all tests (not strictly all) have performed and passed.
* RC1(リリース候補1), RC2 などの若いリリース候補のテスト結果はそのままRC3などへ受け継がれる。つまり古いリリース候補でのテスト結果がでればそのパッケージはリリース許可される。新しくテストを行っても良い。
+
* If RC1 has passed the test, we do not necessarily do tests for RC2, and RC3 ... etc. Of course it's better to do tests for each release candidates.
* 最終判断はQA管理者が行う。
+
* Final decision will be done by the QA manager.
 +
* How we define these tests? (or how to make consensus?)...the QA manager defines. We ja project defined by IRC meetings.
  
==担当者==
+
==Who is in chage and time table==
担当の欄を変更する場合は、QA担当者、日本語プロジェクトリードへ必ず知らせてください。担当欄が()に
+
Please send the QA correspondence and/or the project lead of JA if you want to modify this table
なっているものははQA管理者が割り当てを行っておらず、個々人の判断でやっているものです。
+
  
 
{| border="1" cellpadding="2" cellspacing="0"
 
{| border="1" cellpadding="2" cellspacing="0"
!style="background:#E3E3E3;" |仕事
+
!style="background:#E3E3E3;" |TODO
!style="background:#E3E3E3;" |担当
+
!style="background:#E3E3E3;" |Who
!style="background:#E3E3E3;" |日時
+
!style="background:#E3E3E3;" |Date
!style="background:#E3E3E3;" |タイミング
+
!style="background:#E3E3E3;" |Timing
!style="background:#E3E3E3;" |メモ
+
!style="background:#E3E3E3;" |memo
 
|-
 
|-
|QA管理者の任命||maho|| 2007/11/5  ||    || [http://ja.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=16077 告知] : maho@openoffice.orgが管理者
+
|Appoint QA manager||maho|| 2007/11/5  ||    || [http://ja.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=16077 notification] : maho@openoffice.org is the QA manager
 
|-
 
|-
|QA/release用wiki作成||enoki|| 2008/11/20 || || [http://ja.openoffice.org/servlets/ReadMsg?list=qa&msgNo=15 告知]
+
|creation of wiki for QA/release ||enoki|| 2008/11/20 || || [http://ja.openoffice.org/servlets/ReadMsg?list=qa&msgNo=15 notification]
 
|-
 
|-
|リリースストッパーIssue告知|| maho || 2008/11/25 ||出次第なるべく早く || [http://ja.openoffice.org/servlets/ReadMsg?list=qa&msgNo=35 告知]
+
|Notify the release stopper issue|| maho || 2008/11/25 || ASAP || [http://ja.openoffice.org/servlets/ReadMsg?list=qa&msgNo=35 Notificaton]
 
|-
 
|-
|VCLTestTool環境||  ||  || - ||  
+
|VCLTestTool Environment||  ||  || - ||  
 
|-
 
|-
|リリース候補ビルド告知|| maho || 2008/11/25 || release@でアナウンスあれば || [http://ja.openoffice.org/servlets/ReadMsg?list=qa&msgNo=36 告知]
+
|Notify RC builds || maho || 2008/11/25 || Watch release@ ML || [http://ja.openoffice.org/servlets/ReadMsg?list=qa&msgNo=36 Notification]
 
|-
 
|-
|QATrackへのビルドサブミット|| maho ||2008/11/25  ||  リリース候補ビルド告知と同時期 || [http://ja.openoffice.org/servlets/ReadMsg?list=qa&msgNo=37 方法]
+
|Submit builds to QATrack|| maho ||2008/11/25  ||  RC builds || [http://ja.openoffice.org/servlets/ReadMsg?list=qa&msgNo=37 howto]
 
|-
 
|-
|QA参加者募集|| maho || 2008/11/26 ||  || [http://ja.openoffice.org/servlets/ReadMsg?list=announce&msgNo=303 告知]
+
|Invite QA participants|| maho || 2008/11/26 ||  || [http://ja.openoffice.org/servlets/ReadMsg?list=announce&msgNo=303 notification]
 
|-
 
|-
|QAIRC会議||||    || || なし
+
|QAIRC meeting||||    || || -
 
|-
 
|-
|QA開始|| 全員 ||  || RCが出たらすぐ ||  
+
|Start QA || all ||  || RC1  ||  
 
|-
 
|-
|QA状況報告@QATrack|| maho ||  || テスト結果が大体そろったら   || [http://ja.openoffice.org/servlets/ReadMsg?list=qa&msgNo=91 告知]
+
|QA status update@QATrack|| maho ||  || Test has almost finished   || [http://ja.openoffice.org/servlets/ReadMsg?list=qa&msgNo=91 notification]
 
|-
 
|-
|Distribute Issue作成|| maho || 2008/12/2  || テスト結果が大体揃ったら || [http://ja.openoffice.org/servlets/ReadMsg?list=qa&msgNo=91 告知]
+
|Distribute Issue|| maho || 2008/12/2  || Test has almost finished || [http://ja.openoffice.org/servlets/ReadMsg?list=qa&msgNo=91 notification]
 
|-
 
|-
|リリースアナウンス作成||  maho|| 2008/12/3- ||  Bouncerリンクを確認後 ||  [http://ja.openoffice.org/servlets/ReadMsg?list=qa&msgNo=92 ドラフト]
+
|Release announce||  maho|| 2008/12/3- ||  Bouncer links ||  [http://ja.openoffice.org/servlets/ReadMsg?list=qa&msgNo=92 draft]
 
|-  
 
|-  
|英語版リリースアナウンス翻訳および配信||  (reiko) || 2008/11/18  ||  英後版リリース出次第  || [http://ja.openoffice.org/servlets/ReadMsg?list=announce&msgNo=301 告知]  
+
|Translation & publish of announcement of ENUS ver.||  (reiko) || 2008/11/18  ||  en-us released  || [http://ja.openoffice.org/servlets/ReadMsg?list=announce&msgNo=301 notification]  
 
|-
 
|-
|ダウンロードページ更新|| maho || 2008/12/3-5 || アナウンス直前   || [http://ja.openoffice.org/download/2.4.2/ 2.4.2ダウンロードページ]
+
|Update download page|| maho || 2008/12/3-5 || Before annoucement   || [http://ja.openoffice.org/download/2.4.2/ 2.4.2 download page]
 
|-
 
|-
|トップページ更新|| maho || 2008/12/5 || アナウンス直前 || 旧版なので一ヶ所 [http://ja.openoffice.org/source/browse/ja/www/project_tools.html]
+
|Update top page|| maho || 2008/12/5 || Before announcement || [http://ja.openoffice.org/source/browse/ja/www/project_tools.html]
 
|-
 
|-
|トップページ/ダウンロードページ更新確認||  ||  ||  || (リリース時には比較的タイムラグがある)
+
|Verify topage and download page||  ||  ||  || May have some time lags.
 
|-
 
|-
|リリースアナウンス発信 || maho  || 2008/12/5 ||    || [http://ja.openoffice.org/servlets/ReadMsg?list=announce&msgNo=306 (2.4.2 アナウンス)]
+
|Publish announcement|| maho  || 2008/12/5 ||    || [http://ja.openoffice.org/servlets/ReadMsg?list=announce&msgNo=306 (2.4.2 announcement)]
 
|-
 
|-
|アップデートページ確認|| maho || 2008/12/5 ||  || アップデートページなし? <!-- [http://update.services.openoffice.org/ooo/30_ja.html アップデートページ]  [http://www.openoffice.org/issues/show_bug.cgi?id= #i] -->
+
|Verify update page|| maho || 2008/12/5 ||  || No update page? <!-- [http://update.services.openoffice.org/ooo/30_ja.html update page]  [http://www.openoffice.org/issues/show_bug.cgi?id= #i] -->
 
|-
 
|-
|追加リリース||  || 随時 ||  ||
+
|other releases||  || ||  ||
 
|-
 
|-
 
|-
 
|-
|QAページの歴史に追加|| maho || 2008/12/5 ||  2.4.2リリース作業終わり次第 ||
+
|Add history|| maho || 2008/12/5 ||  After 2.4.2 finished ||
 
|-
 
|-
|次のリリースのwiki作成|| enoki ||  || ||  
+
|Next wiki|| enoki ||  || ||  
 
|}
 
|}
  
==参考リンク==
+
==Links==
 
* Bouncer/ダウンロード回数/ミラーサーバ状況
 
* Bouncer/ダウンロード回数/ミラーサーバ状況
 
** [http://wiki.services.openoffice.org/wiki/Bouncer Bouncerについて]
 
** [http://wiki.services.openoffice.org/wiki/Bouncer Bouncerについて]

Latest revision as of 14:39, 13 January 2009

About QA and release

To release your native language version of OpenOffice.org, each language project proceeds QA (quality assurance). Each native language projects are correspondence and responsible for the release.

For example, the Japanese language project is responsible for Japanese version of OpenOffice.org.

References

Primary information about release candidates and release status

You can obtain information about availability release candidates and their status at Release status minites and release mailing list .

Release QA status of build : QATrack

The QATrack has all information for QA of your language; e.g., in QA, build has been approved, and distributed.

Login to QATrack required. Username and password are the same as when you login to OpenOffice.org site.

Release schedule of US English version of 2.4.2

Where to download 2.4.2 release candidate(s)

Currently we have 2.4.2 release candidate 1. You can download packages from the following links. Note: For English (US) version, the release candidate 1 has been released as the final.

Release stopper issue for 2.4.2

http://www.openoffice.org/issues/show_bug.cgi?id=94185

Note: this issue has already been closed.

If you found a show stopper (critical bug) for 2.4.2,

  • Write an issue and depend on the issue,
  • And explain why you think this is a stopper at releases@openoffice.org.

Reference

VCL TestTool for 2.4.2

VCL TestTool Binaries OOo 2.4 / OOo 3.x Please download VCL TestTool binary from the link above.

VCL TestTool environment for 2.4.2

OOo 2.4.2用 VCLTestTool Environment

MD5SUM of the VCLTestTool environment

This a checkout by Andre Schnabel.

References

  1. about tag: For Builds >= DEV300m14 use HEAD
  2. Update every day by Andre Schnabel
  3. Announcement by Andre Schnabel
  4. CVS tag and branches(How we can checkout VCLTestTool environment)

How you test 2.4.2 release candidates and how release candidates get approved

We JA project define the following three tests for approval of the release candidates

Release criterion

  • One release candidate must be tested at least one of the method described above.
  • Almost all tests (not strictly all) have performed and passed.
  • If RC1 has passed the test, we do not necessarily do tests for RC2, and RC3 ... etc. Of course it's better to do tests for each release candidates.
  • Final decision will be done by the QA manager.
  • How we define these tests? (or how to make consensus?)...the QA manager defines. We ja project defined by IRC meetings.

Who is in chage and time table

Please send the QA correspondence and/or the project lead of JA if you want to modify this table

TODO Who Date Timing memo
Appoint QA manager maho 2007/11/5 notification : maho@openoffice.org is the QA manager
creation of wiki for QA/release enoki 2008/11/20 notification
Notify the release stopper issue maho 2008/11/25 ASAP Notificaton
VCLTestTool Environment -
Notify RC builds maho 2008/11/25 Watch release@ ML Notification
Submit builds to QATrack maho 2008/11/25 RC builds howto
Invite QA participants maho 2008/11/26 notification
QAIRC meeting -
Start QA all RC1
QA status update@QATrack maho Test has almost finished notification
Distribute Issue maho 2008/12/2 Test has almost finished notification
Release announce maho 2008/12/3- Bouncer links draft
Translation & publish of announcement of ENUS ver. (reiko) 2008/11/18 en-us released notification
Update download page maho 2008/12/3-5 Before annoucement 2.4.2 download page
Update top page maho 2008/12/5 Before announcement [1]
Verify topage and download page May have some time lags.
Publish announcement maho 2008/12/5 (2.4.2 announcement)
Verify update page maho 2008/12/5 No update page?
other releases
Add history maho 2008/12/5 After 2.4.2 finished
Next wiki enoki

Links

Personal tools