Jump to: navigation, search

Difference between revisions of "Incubator Hatching"

 
Line 11: Line 11:
 
Some initial thoughts on this topic were discussed on the
 
Some initial thoughts on this topic were discussed on the
 
[http://dev.eclipse.org/mhonarc/lists/wtp-pmc/msg00527.html WTP PMC mailing list].
 
[http://dev.eclipse.org/mhonarc/lists/wtp-pmc/msg00527.html WTP PMC mailing list].
 +
 +
== Hatching Checklist ==
 +
 +
The following list contains the proposed criteria for hatching:
 +
 +
# The code should be of good quality and all proposed API should have Javadoc.
 +
# There should be a suite of JUnit tests that provide adequate coverage.
 +
# The builds should be integrated into the WTP build infrastructure and the JUnits should run and pass. This implies the code will be upgraded to the current WTP level and will track WTP weekly, i.e. I-builds succeed.
 +
# The tutorials should be clear enough so that even a PMC member can follow them successfully. :-)
 +
# PMC members (and other members of WTP) should evaluate the code based on the tutorials and report favorably.
 +
# A committer vote should pass favourably when the project is ready to hatch.

Revision as of 10:33, 16 May 2006

Introduction

WTP is currently hosting several incubator projects:

  • JSF Tools
  • Dali JPA Tools
  • AJAX Tools Framework

It would therefore be a good idea if we spelled out what we expect from these projects so they can "hatch" into full-fledged components of WTP.

Some initial thoughts on this topic were discussed on the WTP PMC mailing list.

Hatching Checklist

The following list contains the proposed criteria for hatching:

  1. The code should be of good quality and all proposed API should have Javadoc.
  2. There should be a suite of JUnit tests that provide adequate coverage.
  3. The builds should be integrated into the WTP build infrastructure and the JUnits should run and pass. This implies the code will be upgraded to the current WTP level and will track WTP weekly, i.e. I-builds succeed.
  4. The tutorials should be clear enough so that even a PMC member can follow them successfully. :-)
  5. PMC members (and other members of WTP) should evaluate the code based on the tutorials and report favorably.
  6. A committer vote should pass favourably when the project is ready to hatch.