Difference between revisions of "Eclipse/Release checklist"

From Eclipsepedia

Jump to: navigation, search
m
Line 98: Line 98:
 
   <li><b>Make sure all bugs with patches have the iplog+ flag set</b>
 
   <li><b>Make sure all bugs with patches have the iplog+ flag set</b>
 
     <ul>
 
     <ul>
       <li>For instructions see [http://dev.eclipse.org/mhonarc/lists/eclipse-dev/msg08253.html Clarification on use of iplog flag ]</li>
+
       <li>For instructions see [[Eclipse/Bug_Tracking#Tracking_IP_Contributions]]</li>
 
     </ul>
 
     </ul>
 
   </li>
 
   </li>

Revision as of 10:20, 28 May 2010

This checklist is used by the Eclipse top-level project in preparing its releases.

  1. Copyright notices
    • All source files must have appropriate EPL v1.0 copyright notice
    • Source files whose content was created in this release should read "Copyright (c)  2009 ..." or "Copyright (c)  2010 ..."
    • Source files whose content was modified during this release should read "Copyright (c)  200x, 2009 ..." or "Copyright (c)  200x, 2010 ..."
    • Ok green.gif All features should have "(c) Copyright Eclipse contributors and others 2000, 2010." in Help > About Eclipse SDK
    • Ok green.gif Splash screen copyright needs to be updated
  2. Ok green.gif Plug-in and feature identification [Dani]
    • Check the info in Help > About Eclipse SDK
    • All features should have provider "Eclipse.org" and a version that adheres to the Versioning guidelines
    • All plug-ins should have provider "Eclipse.org" and version Versioning guidelines, except for known special cases (org.apache.*, org.junit, and bundles from Orbit).
  3. Ok green.gif License agreements for features and plug-ins [Dani]
    • Help > About Eclipse SDK > {Feature | Plug-in} Details > More Info
    • All features should link to the Eclipse Foundation Software User Agreement dated April 14, 2010
    • All plug-ins should link to the plug-in's about.html file containing its plug-in-specific license
  4. Extension point documentation
    • Extension points must be documented in the appropriate help book
      • Platform Plug-in Developer Guide; section Reference / Extension Points Reference
      • JDT Plug-in Developer Guide; section Reference / Extension Points Reference
      • PDE Guide; section Reference / Extension Points Reference
    • Must be a link to each extension point that a component has
    • Extension points added in this release must be clearly marked "Since x.y" where x.y is the project release number
    • See also ISV doc checklist
  5. API documentation
    • Java API must be documented in the appropriate help book
      • Platform Plug-in Developer Guide; section Reference / API Reference
      • JDT Plug-in Developer Guide; section Reference / API Reference
      • PDE Guide; section Reference / API Reference
    • Must be a link to each API package that a component has
    • API package must have package overview (package.html)
    • All API elements must be documented
    • API elements added in this release must be tagged "@since x.y" where x.y is the bundle version number
    • See also ISV doc checklist and code checklist
  6. User Documentation
  7. API Compatibility
    • Make sure that the 'API Tools Version Verification Report' lists no compatibility and no bundle version warning for your bundles
    • Verify that the 'API Tools Post-API Freeze Report' has no entries
  8. Plug-in Migration Guide
    • Instructions for migrating older plug-ins to current release
    • Must describe incompatibilities and breaking API changes
    • Should describe deprecations and places where current release has a better story that plug-ins should more to
    • Located in Platform Plug-in Developer Guide / Porting Guide
    • Remove old migration guide if necessary (we generally keep three years of migration guides available in each release)
  9. What's New [JohnA]
    • Describes the more interesting differences that users will see when they upgrade to the latest release
    • Located in {Workbench | Java Development | PDE} User Guide / What's new
  10. Make sure all bugs with patches have the iplog+ flag set
  11. Submit the IP Log to Eclipse Legal [JohnA]
  12. Eclipse Project Release Notes
    • Add known problems for each component and other late-breaking news for customers of this release
    • See bug 313131 for details
    • Update other sections of readme based on current release plan [JohnA]
  13. Source builds
    • Verify that source builds compile and work on all reference platforms.
  14. Verify that source is included in all SDK features
  15. Test updating from update site to platform runtime to other eclipse SDK and runtime features on reference platforms and assorted VMs
  16. Test the version of PDE build in basebuilder to ensure there aren't any errors
  17. Verify that all the "abouts" in the Platform, RCP, SDK and CVS features sow the correct release name in the about
  18. Produce the release review documentation [JohnA]