Difference between revisions of "Release criteria"
From Apache OpenOffice Wiki
(Created page with 'Product Releases of OpenOffice.org are downloaded by millions of users, are integrated into complex business solutions and are published by different Linux distributions arou…') |
|||
| (30 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
[[Product Release]]s of OpenOffice.org are downloaded by millions of users, are integrated into complex business solutions and are published by different Linux distributions around the world. Therefore a Release of OOo has to fulfill a lot of requirements. Over the past years many requirements came up and this should be a collection. | [[Product Release]]s of OpenOffice.org are downloaded by millions of users, are integrated into complex business solutions and are published by different Linux distributions around the world. Therefore a Release of OOo has to fulfill a lot of requirements. Over the past years many requirements came up and this should be a collection. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
= Meaning = | = Meaning = | ||
| − | Release Criteria should address the most critical aspects which are important for a Release of OpenOffice.org. Many areas have to be checked by the Release Manager or others before a release approval can be given. All items on this page are needed to be fulfilled before a release approval. But it is possible that one or more items are not fulfilled and a release is approved. Then the Release Status Meeting | + | Release Criteria should address the most critical aspects which are important for a Release of [[OpenOffice.org]]. Many areas have to be checked by the [[Release Manager]] or others before a release approval can be given. All items on this page are needed to be fulfilled before a release approval. But it is possible that one or more items are not fulfilled and a release is approved. Then the Release Status Meeting has given the approval. |
= Responsibilities = | = Responsibilities = | ||
| − | * The Release Managers and the Release Status Meeting approve the general Release of OOo. This means that the English version and the source of OOo is approved. Then there isn't planned any further build for such release. All | + | * The Release Managers and the [http://wiki.services.openoffice.org/wiki/ReleaseStatus_Minutes Release Status Meeting] approve the general Release of OOo. This means that the English version and the source of OOo is approved. Then there isn't planned any further build for such release. All other languages have to be released on such code base. |
| − | * Other languages are approved by the corresponding Localization (L10N) | + | * Other languages are approved by the corresponding [http://projects.openoffice.org/native-lang.html Localization teams] (L10N). If this isn't done, a language build will stay in unstable status of a Release Candidate and isn't available via the [http://download.openoffice.org general download link]. |
| Line 23: | Line 14: | ||
== Quality requirements == | == Quality requirements == | ||
=== Automated testing [http://quaste.services.openoffice.org QUASTe] === | === Automated testing [http://quaste.services.openoffice.org QUASTe] === | ||
| − | * The 'required' tests | + | * The 'required' tests have to run without any error and warning in the English version (more languages are welcome) |
* The 'optional' tests should run without any error and warning in the English version (more languages are welcome) | * The 'optional' tests should run without any error and warning in the English version (more languages are welcome) | ||
=== General testing === | === General testing === | ||
| − | * TCM testing should be finalized for one or more languages without any [[Stopper]] | + | * [http://wiki.services.openoffice.org/wiki/Test_Case_Management TCM] testing should be finalized for one or more languages without any [[Stopper]] issue |
| − | * All | + | * All installation sets are checked generally (MD5 checksums etc. are available) |
| − | * There is not any | + | * There is not any issues in [http://qa.openoffice.org/issues/query.cgi IssueTracker] open for the corresponding release target |
| − | * There is not any CWS in EIS open for the corresponding release target | + | * There is not any [[ChildWorkSpace|CWS]] in [http://eis.services.openoffice.org EIS] open for the corresponding release target |
| − | === [[Stopper]] | + | === [[Stopper]] issues === |
* There is not any opened and known <b>Stopper</b> issues for this release | * There is not any opened and known <b>Stopper</b> issues for this release | ||
| − | * The last <b>Release Candidate</b> is available for longer than 5 days and there is not any new announced and approved <b>Stopper</b> in the Releases mailing list (releases @openoffice.org) | + | * The last <b>Release Candidate</b> is available for longer than 5 days (including one weekend) and there is not any new announced and approved <b>Stopper</b> in the Releases mailing list (releases @openoffice.org) |
== Localization requirements== | == Localization requirements== | ||
| + | ===Conditions=== | ||
* English is source language and has to be 100% translated in User Interface (UI) and Online Help (Help) | * English is source language and has to be 100% translated in User Interface (UI) and Online Help (Help) | ||
| − | * | + | * Translation and the testing of the localized builds has to be finished before the first Release Candidate will be published |
| − | * <b>but</b> | + | * Official installation sets for localized builds will be provided when |
| + | ** 100% in UI and Help is translated <b>but</b> | ||
| + | ** <b>Full install sets</b> for a language can be requested when UI and Help are at least 80% translated | ||
| + | ** [[Languagepack | Language packs]] can be requested when only UI is at least 80% translated | ||
| + | ** <b>Language packs</b> will be done when full install sets are built, too | ||
| + | |||
| + | ===References=== | ||
| + | * As reference the percent values from the Pootle servers will be used (see section [https://tools.services.openoffice.org "Translation Pootle Server"]). Depending on the language Pootle or Pootle2 has to be used. | ||
| + | * Information about the [http://wiki.services.openoffice.org/wiki/NLC:ReleaseChecklist Release Process of a localized build] can be found in the Native Language Confederation ([[NLC]]) category. | ||
| Line 48: | Line 48: | ||
== Technical requirements == | == Technical requirements == | ||
| − | * collab.net is informed about the release early enough | + | * [http://www.collab.net Collab.net] is informed about the release early enough |
| − | * | + | * Installation sets are linked to the final place for download |
| − | * | + | * Links are working on the [http://download.openoffice.org general download website] |
== Marketing requirements == | == Marketing requirements == | ||
* Release notes are ready | * Release notes are ready | ||
| − | * | + | * Websites for the Release are ready and present |
| + | |||
| + | [[Category:Releases]] | ||
Latest revision as of 23:29, 11 April 2011
Product Releases of OpenOffice.org are downloaded by millions of users, are integrated into complex business solutions and are published by different Linux distributions around the world. Therefore a Release of OOo has to fulfill a lot of requirements. Over the past years many requirements came up and this should be a collection.
Contents
Meaning
Release Criteria should address the most critical aspects which are important for a Release of OpenOffice.org. Many areas have to be checked by the Release Manager or others before a release approval can be given. All items on this page are needed to be fulfilled before a release approval. But it is possible that one or more items are not fulfilled and a release is approved. Then the Release Status Meeting has given the approval.
Responsibilities
- The Release Managers and the Release Status Meeting approve the general Release of OOo. This means that the English version and the source of OOo is approved. Then there isn't planned any further build for such release. All other languages have to be released on such code base.
- Other languages are approved by the corresponding Localization teams (L10N). If this isn't done, a language build will stay in unstable status of a Release Candidate and isn't available via the general download link.
Guidelines/Criteria
Quality requirements
Automated testing QUASTe
- The 'required' tests have to run without any error and warning in the English version (more languages are welcome)
- The 'optional' tests should run without any error and warning in the English version (more languages are welcome)
General testing
- TCM testing should be finalized for one or more languages without any Stopper issue
- All installation sets are checked generally (MD5 checksums etc. are available)
- There is not any issues in IssueTracker open for the corresponding release target
- There is not any CWS in EIS open for the corresponding release target
Stopper issues
- There is not any opened and known Stopper issues for this release
- The last Release Candidate is available for longer than 5 days (including one weekend) and there is not any new announced and approved Stopper in the Releases mailing list (releases @openoffice.org)
Localization requirements
Conditions
- English is source language and has to be 100% translated in User Interface (UI) and Online Help (Help)
- Translation and the testing of the localized builds has to be finished before the first Release Candidate will be published
- Official installation sets for localized builds will be provided when
- 100% in UI and Help is translated but
- Full install sets for a language can be requested when UI and Help are at least 80% translated
- Language packs can be requested when only UI is at least 80% translated
- Language packs will be done when full install sets are built, too
References
- As reference the percent values from the Pootle servers will be used (see section "Translation Pootle Server"). Depending on the language Pootle or Pootle2 has to be used.
- Information about the Release Process of a localized build can be found in the Native Language Confederation (NLC) category.
Legal requirements
- All legal requirements for the product have been cleared (3rd party software etc.)
Technical requirements
- Collab.net is informed about the release early enough
- Installation sets are linked to the final place for download
- Links are working on the general download website
Marketing requirements
- Release notes are ready
- Websites for the Release are ready and present
