[This is under development; and I'm very narrow sighted person, thus feed back is very very very welcome]
1. How to get started with QA? What is QA? QA is Quality Assurance. What is Quality? Quality product doesn't crash. What is Assurance? To make sure it doesn't crash. How to QA? Follow the following 5 steps: 1. Subscribe releases/AT/openoffice.org and watch out its announcements. 2. When announced, find your localized snapshot build or release candidate. 3. Download and Install it onto your machine and start it. Then you have done the first and the most important part of QA. 4. Tell your community QA lead what you have done and results. 5. If you can not find your QA lead, be QA lead yourself. How to be QA lead? Declare at your local mailing list and be accepted. What QA lead does? Tell dev/AT/qa.openoffice.org that you are QA lead, and ask many questions on the list, and ask your community members for help. You want to do more? Sure, there are TCM, QAtrack, TestTool, IssueTracker and various mailing lists you can contribute. What are these things? Time-consuming things. You need skill to do them. You need to read a lot. You need to ask a lot of questions. Are you still here? :) Good! Then let's get started. Quick! Start asking Questions! (dedicated by Hirano Kazunari) 2. The QA process. For each localized builds, quality assurance (QA) must be passed to official release of the builds. Each native language team, localization team and porting team must elect QA responsibility person(s) to conduct QA. QA responsibility person must test release candidate (RC) builds, and do some test, if test is done, then say "GO", and released. 2. Availability of builds The Hamburg release engineering team volunteer for providing packages for Windows, GNU/Linux and Solaris (i386/Sparc). For other platforms, for example MacOSX porting team provides MacOSX builds. Such informations can be obtained at [EMAIL PROTECTED] For example, announcements of OpenOffice.org 2.1RC2 packages at [EMAIL PROTECTED] are: * http://www.openoffice.org/servlets/ReadMsg?list=releases&msgNo=10261 * http://www.openoffice.org/servlets/ReadMsg?list=releases&msgNo=10273 3. Which packages should be QA'ed? For example, there are some packages for Japanese(and or your fav. lang) for OOo2.1RC2. GNU/Linux * OOo_2.1.0rc2_20061130_LinuxIntel_install_ja.tar.gz * OOo_2.1.0rc2_20061201_LinuxIntel_install_ja_wJRE.tar.gz * OOo_2.1.0rc2_20061201_LinuxIntel_langpack_ja.tar.gz Windows * OOo_2.1.0rc2_20061130_Win32Intel_install_ja.exe * OOo_2.1.0rc2_20061130_Win32Intel_install_ja_wJRE.exe * OOo_2.1.0rc2_20061130_Win32Intel_langpack_ja.exe Solaris (Sparc) * OOo_2.1.0rc2_20061130_SolarisSparc_install_ja.tar.gz * OOo_2.1.0rc2_20061130_SolarisSparc_install_ja_wJRE.tar.gz * OOo_2.1.0rc2_20061130_SolarisSparc_langpack_ja.tar.gz Solaris (x86) * OOo_2.1.0rc2_20061201_Solarisx86_install_ja.tar.gz * OOo_2.1.0rc2_20061201_Solarisx86_install_ja_wJRE.tar.gz * OOo_2.1.0rc2_20061201_Solarisx86_langpack_ja.tar.gz MacOSX * OOo_2.1.0rc2_20061130_MacOSXIntel_install_ja.dmg * OOo_2.1.0rc2_20061130_MacOSXPPC_install_ja.dmg 3. Trigger for QA Availability of builds immediately means QA process can be started. Each native language team, localization team and porting team should immediately elect QA responsibility person(s) to conduct QA. 4. What should do in QA for release? It is up to QA responsibilities. We respect decision by QA responsibilities. Here are some recommended way of tests * Using TCM (Test Case Management). How to use TCM? http://wiki.services.openoffice.org/wiki/Test_Case_Management * Using automated QAtool. How to use QAtesttool for personal use? See [QA] for example. We recommend to use TCM. 5. Tracking QA QA status of localized builds can be found at http://www.qatrack.org/ooo/view.php 6. Writing Issue If some localized builds are approved, you should write an issue so that distribute QA'ed packages are distributed worldwide (congratulations!) Here is a list that request packages are QA'ed and mark as `release' and distribute to the mirrors. How to write issues? You should learn from following issues. Esp. http://www.openoffice.org/issues/show_bug.cgi?id=72468 (German) might help you ;) http://www.openoffice.org/issues/show_bug.cgi?id=72735 (MacOSX en-US PPC) http://www.openoffice.org/issues/show_bug.cgi?id=72586+72547+72490 (Polish) http://www.openoffice.org/issues/show_bug.cgi?id=72586 (Irish) http://www.openoffice.org/issues/show_bug.cgi?id=72548 (Dutch) http://www.openoffice.org/issues/show_bug.cgi?id=72525 (French) http://www.openoffice.org/issues/show_bug.cgi?id=72496 (Norwegian) http://www.openoffice.org/issues/show_bug.cgi?id=72478 (Italian) http://www.openoffice.org/issues/show_bug.cgi?id=72468 (German) [Useful Links] * http://wiki.services.openoffice.org/wiki/Test_Case_Management (TCM) * http://wiki.services.openoffice.org/wiki/QA_Metrics * http://wiki.services.openoffice.org/wiki/Automating_Translation_QA#Support_in_translation_tools * http://wiki.services.openoffice.org/wiki/Release_Action_List_for_QA * http://wiki.services.openoffice.org/wiki/NLC/localizedQA For person who is interested in QAtesttool, some concrete method have been described [QA] http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7469 http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7433 http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7490 http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7491 http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7492 http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7494 http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7553 http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7672 thanks -- NAKATA, Maho ([EMAIL PROTECTED]) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
