Difference between revisions of "Release Action List for QA"
From Apache OpenOffice Wiki
Pereriksson (Talk | contribs) (updated and refreshed) |
|||
| (8 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | [[Category:Quality Assurance]] | |
| − | project in a release cycle of OOo. | + | |
| − | + | This list should be a collection of action items for the OpenOffice.org QA project in a release cycle of OOo. | |
| − | OOo. The release maps can be found at OOo wiki on Quality Assurance page | + | |
| − | ([[ | + | The action items are based on the release maps for each release of OOo. The release maps can be found at OOo wiki on Quality Assurance page |
| − | + | (e.g. [[OOoRelease241]]). | |
| − | + | ||
| − | release announcement. | + | == Developer Snapshot == |
| − | + | Sun Team will provide a list of all integrated features in the release announcement. | |
| − | + | ||
| − | + | == Feature Freeze and/or UI Freeze == | |
| − | + | For the next build after Feature Freeze and/or UI Freeze a list of all integrated features has to be announced on the [mailto:dev@qa.openoffice.org dev@qa.openoffice.org] mailing list. | |
| − | all integrated features has to be announced on the | + | * The list will be provided by Sun team. |
| − | + | * Also Features/UI changes which have missed this deadline will be announced in this list too (start discussion about shifting these features to next release) | |
| − | + | * The L10N teams should use the list to organize the translation of the new features. | |
| − | missed this deadline will be announced in this list too (start | + | * The QA teams can use the list for extending testing of the new features (Translations are only final and integrated for English and German) |
| − | discussion about shifting these features to next release) | + | |
| − | + | == Code Freeze == | |
| − | organize the translation of the new features | + | The next build after Code Freeze a list of all integrated features has to be announced on the [mailto:dev@qa.openoffice.org dev@qa.openoffice.org] mailing list. |
| − | + | * The list will be provided by Sun team | |
| − | extending testing of the new features (Translations are only final | + | * Also Features/UI changes which have missed this deadline will be announced in this list (final agreements for integrating or shifting these features has to exist) |
| − | and integrated for English and German) | + | * The translation of all new features can be tested in a separate L10N build or in the master build (a separate announcement for L10N testing). |
| − | + | * At this point it is the last chance to stop new feature implementation | |
| − | + | ||
| − | + | == Release Candidate == | |
| − | + | For each Release Candidate the results of automated testing on that build will be announced in the [mailto:dev@qa.openoffice.org dev@qa.openoffice.org] mailing list | |
| − | has to be announced on the | + | |
| − | + | Currently an unformal mail will be provided by Sun QA team (perhaps in the future a tooling on OOo can provided these list automatically) | |
| − | + | ||
| − | missed this deadline will be announced in this list (final agreements | + | == Approval of Builds == |
| − | for integrating or shifting these features has to exist) | + | |
| − | + | Every build that should be distributed as offical needs to be QA'ed and approved for release. For more information, see [http://qa.openoffice.org/localized/index.html QA Process for Localized Builds]. | |
| − | can be tested in a separate L10N build or in the master build (a | + | |
| − | separate announcement for L10N testing) | + | Set the status to APPROVED for each build that is approved for distribution in [http://qatrack.services.openoffice.org/ OpenOffice.org QATrack]. |
| − | + | ||
| − | stop new feature implementation | + | To get an approved build distributed to the mirror network an issue needs to be filed. Use |
| − | + | [http://qa.openoffice.org/issues/enter_bug.cgi?comment=following%20builds%20of%20%3Cversion%3ERC%3Cnr%3E%20%3Clocalization%3E%20have%20passed%20QA%20and%20should%20be%0D%0Adistributed%20to%20the%20mirror%20network%20as%20stable%20builds%3A%0D%0A%3Curl1%3E%0D%0A%3Curl2%3E%20%0D%0A%0D%0A...;issue_type=TASK;rep_platform=All;op_sys=All;priority=P3;subcomponent=www;component=qa;version=OOo%202.0;short_desc=Distribute%20%3Cversion%3ERC%3Cnr%3E%20-%20%3Clang%3E%20localization%20as%20final;form_name=enter_issue this link] as a template. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | that build will be announced in the | + | |
| − | + | ||
| − | provided by Sun QA team (perhaps in the future a tooling on OOo can | + | |
| − | provided these list automatically) | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Latest revision as of 22:35, 17 July 2008
This list should be a collection of action items for the OpenOffice.org QA project in a release cycle of OOo.
The action items are based on the release maps for each release of OOo. The release maps can be found at OOo wiki on Quality Assurance page (e.g. OOoRelease241).
Contents
Developer Snapshot
Sun Team will provide a list of all integrated features in the release announcement.
Feature Freeze and/or UI Freeze
For the next build after Feature Freeze and/or UI Freeze a list of all integrated features has to be announced on the dev@qa.openoffice.org mailing list.
- The list will be provided by Sun team.
- Also Features/UI changes which have missed this deadline will be announced in this list too (start discussion about shifting these features to next release)
- The L10N teams should use the list to organize the translation of the new features.
- The QA teams can use the list for extending testing of the new features (Translations are only final and integrated for English and German)
Code Freeze
The next build after Code Freeze a list of all integrated features has to be announced on the dev@qa.openoffice.org mailing list.
- The list will be provided by Sun team
- Also Features/UI changes which have missed this deadline will be announced in this list (final agreements for integrating or shifting these features has to exist)
- The translation of all new features can be tested in a separate L10N build or in the master build (a separate announcement for L10N testing).
- At this point it is the last chance to stop new feature implementation
Release Candidate
For each Release Candidate the results of automated testing on that build will be announced in the dev@qa.openoffice.org mailing list
Currently an unformal mail will be provided by Sun QA team (perhaps in the future a tooling on OOo can provided these list automatically)
Approval of Builds
Every build that should be distributed as offical needs to be QA'ed and approved for release. For more information, see QA Process for Localized Builds.
Set the status to APPROVED for each build that is approved for distribution in OpenOffice.org QATrack.
To get an approved build distributed to the mirror network an issue needs to be filed. Use this link as a template.
