Jump to: navigation, search

Development Resources/HOWTO/Graduation Reviews

< Development Resources
Revision as of 11:45, 24 August 2010 by Wayne.eclipse.org (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
See 6.3.2 Graduation Review" and "6.3 Reviews" in the Eclipse Development Process
The purpose of the Graduation Review is to confirm that the Project is/has:
  • a working and demonstratable code base of sufficiently high quality
  • active and sufficiently diverse communities: adopters, developers, and users
  • operating fully in the open following the Principles and Purposes of Eclipse
  • a credit to Eclipse and is functioning well within the larger Eclipse community

It is a pretty common case that a graduation review is either combined with or leads to a creation review (in the case when a component is turned into a project) or move review (e.g. move from one top-level project to another) or other procedure.

What are the Requirements?

See Development Resources/HOWTO/Criteria for Graduating from Incubation Phase to Mature Phase.

Preparing the Review Document

See Development Resources/FAQs/About Review Documentation.

The document must cover the issues from above especially the formation and viability of the three communities. Most projects combine their Graduation Review with the Release Review of their 1.0 release, in which case the document must also cover the Release Review issues.

The Review Process

Once the review content has been created, the operational side of a Gradation Review is described at Development Resources/HOWTO/Review Process.

After a Successful Review

After a successful advisory vote and the approval of the Graduation Review by the EMO:

  1. the EMO will send email to the project developer mailing list with the approval
  2. the project can remove the "incubation" labeling and logos from their website pages

This page is moderated by the EMO