Difference between revisions of "Development Resources/HOWTO/Graduation Reviews"

From Eclipsepedia

Jump to: navigation, search
(New page: <div style="float: right; border: 1px dashed black; background-color: #FFFFDD;"><table><tr><td width="150px">See [http://www.eclipse.org/projects/dev_process/development_process.php#6_3_...)
 
 
(6 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
<div style="float: right; border: 1px dashed black;  
 
<div style="float: right; border: 1px dashed black;  
background-color: #FFFFDD;"><table><tr><td width="150px">See  
+
background-color: #FFFFDD;"><table><tr><td width="150px">See [http://www.eclipse.org/projects/dev_process/development_process.php#6_3_2_Graduation_Review 6.3.2 Graduation Review]" and "[http://www.eclipse.org/projects/dev_process/development_process.php#6_3_Reviews 6.3 Reviews]" in the Eclipse Development Process</td>
[http://www.eclipse.org/projects/dev_process/development_process.php#6_3_2_Graduation_Review 6.3.2 Graduation Review]" and "[http://www.eclipse.org/projects/dev_process/development_process.php#6_3_Reviews 6.3 Reviews"
+
</tr></table></div>
in the Eclipse Development Process</td>
+
</tr></table></div><blockquote><em>The purpose of the Graduation Review is to confirm that the Project is/has:<ul>
+
<li> a working and demonstratable code base of sufficiently high quality
+
<li> active and sufficiently diverse communities: adopters, developers, and users
+
<li> operating fully in the open following the Principles and Purposes of Eclipse
+
<li> a credit to Eclipse and is functioning well within the larger Eclipse community
+
</ul></em></blockquote>
+
  
===(1) What are the Requirements?===
+
<blockquote><em>The purpose of the Graduation Review is to confirm that the Project is/has:
<span style="margin-right:6px; margin-top:5px; float:left; color:ivory; background:#FF9999;
+
border:1px solid #444; font-size:30px; line-height:25px; padding-top:2px;
+
padding-left:2px; padding-right:2px; font-family:times; ">R</span>See [[Development Resources/HOWTO/Criteria for Graduating from Incubation Phase to Mature Phase]].
+
  
===(2) Preparing the Docuware===
+
* a working and demonstratable code base of sufficiently high quality
See [[Development Resources/FAQs/About Docuware]].
+
* 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
 +
</em></blockquote>
  
<span style="margin-right:6px; margin-top:5px; float:left; color:ivory; background:#FF9999;
+
It is a pretty common case that a graduation review is either combined with or leads to a [[Development Resources/HOWTO/Creation Reviews | creation review]] (in the case when a component is turned into a project) or [[Development_Resources/HOWTO/Review_Information_for_Project_Leads#Move_Reviews | move review]] (e.g. move from one top-level project to another) or other procedure.
border:1px solid #444; font-size:30px; line-height:25px; padding-top:2px;
+
 
padding-left:2px; padding-right:2px; font-family:times; ">R</span><br>The docuware must cover the issues  
+
===What are the Requirements?===
from above especially the formation and viability of the three communities.   
+
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
 
Most projects combine their Graduation Review with the Release Review of
their 1.0 release, in which case the docuware must also cover the  
+
their 1.0 release, in which case the document must also cover the  
[http://www.eclipse.org/projects/dev_process/release-review.php Release Review] issues.
+
[[Development Resources/HOWTO/Release Reviews | Release Review]] issues.
  
===(3) The Review Process===
+
===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]].
 
Once the review content has been created, the operational side of a Gradation Review is described at [[Development Resources/HOWTO/Review Process]].
  
===(4) After a Successful Review===
+
===After a Successful Review===
 
After a successful advisory vote and the approval of the Graduation Review by the EMO:
 
After a successful advisory vote and the approval of the Graduation Review by the EMO:
# the EMO will send email to the project developer mailing list with the approval<
+
# the EMO will send email to the project developer mailing list with the approval
 
# the project can remove [http://www.eclipse.org/projects/dev_process/parallel-ip-process.php#Conforming the "incubation" labeling and logos] from their website pages
 
# the project can remove [http://www.eclipse.org/projects/dev_process/parallel-ip-process.php#Conforming the "incubation" labeling and logos] from their website pages
  
If the Graduation Review was also a Release Review, see [http://www.eclipse.org/projects/dev_process/release-review.php after successful review]" notes those reviews.
+
''This page is moderated by the EMO''
 
+
''This page is moderated by Anne Jacko and Bjorn Freeman-Benson (Eclipse Foundation)''
+
 
[[Category:Development_Resources]]
 
[[Category:Development_Resources]]
 
[[Category:How to Contribute]]
 
[[Category:How to Contribute]]

Latest revision as of 12:45, 24 August 2010

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.

Contents

[edit] What are the Requirements?

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

[edit] 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.

[edit] 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.

[edit] 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