Release criteria

From Apache OpenOffice Wiki
Revision as of 17:38, 11 April 2011 by Hrithik (Talk | contribs)

Jump to: navigation, search

Product Releases of 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.


Release Criteria should address the most critical aspects which are important for a Release of 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.


  • 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.


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

live sex

  • 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

Localization requirements


  • 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


Legal requirements

  • All legal requirements for the product have been cleared (3rd party software etc.)

Technical requirements

Marketing requirements

  • Release notes are ready
  • Websites for the Release are ready and present
Personal tools