Jump to: navigation, search

Difference between revisions of "Eclipse/Release checklist"

m
m
Line 9: Line 9:
 
       <li>All features should have &quot;(c) Copyright Eclipse contributors and  
 
       <li>All features should have &quot;(c) Copyright Eclipse contributors and  
 
         others 2000, 2007.&quot; in Help &gt; About Eclipse Platform</li>
 
         others 2000, 2007.&quot; in Help &gt; About Eclipse Platform</li>
 +
      <li>Also, splash screen copyright needs to be updated, see  [https://bugs.eclipse.org/bugs/show_bug.cgi?id=184622 bug 184622]
 
     </ul>
 
     </ul>
 
   </li>
 
   </li>
Line 99: Line 100:
 
       <li>There were issues with this because of bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=179616 bug 179616]</li>
 
       <li>There were issues with this because of bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=179616 bug 179616]</li>
 
     </ul>
 
     </ul>
 +
  </li>
 +
  </li>
 +
<li><b>Test updates from platform runtime other Eclipse SDK features on reference platforms and VMS</b>
 
   </li>
 
   </li>
  
 
</ol>
 
</ol>

Revision as of 08:02, 8 May 2007

  1. Copyright notices
    • All source files must have appropriate EPL v1.0 copyright notice
    • Source files whose content was created for 3.3 should read "Copyright (c)  2007 ..."
    • Source files whose content was modified during 3.3 cycle should read "Copyright (c)  200x, 2007 ..."
    • All features should have "(c) Copyright Eclipse contributors and others 2000, 2007." in Help > About Eclipse Platform
    • Also, splash screen copyright needs to be updated, see bug 184622
  2. Plug-in and feature identification
    • Check this info from Help > About Eclipse Platform
    • 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).
    • Compare release build with last release 3.2.2 using the version compare tool.
  3. License agreements for features and plug-ins
    • Help > About Eclipse Platform > {Feature | Plug-in} Details > More Info
    • All features should link to the Eclipse Foundation Software User Agreement dated Mar. 17, 2005
    • 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 3.3 must be clearly marked "Since 3.3"
  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 3.3 must be tagged "@since 3.3"
  6. 3.3 Plug-in Migration Guide
    • Instructions for migrating older plug-ins to 3.3
    • Must describe incompatibilities and breaking API changes
    • Should describe deprecations and places where 3.3 has a better story that plug-ins should more to
    • Located in Platform Plug-in Developer Guide / Porting Guide
  7. What's New in 3.3
    • Describes the more interesting differences that 3.2 users will see when they upgrade to 3.3
    • Located in {Workbench | Java Development | PDE} User Guide / What's new
  8. Release notes
    • Know problems for each component and other late-breaking news for customers of 3.3
    • Located in eclipse/readme/readme_eclipse.html
  9. Source builds
    • Verify that source builds compile and work on all reference platforms.
  10. Verify that source is included in all SDK features
    • There were issues with this because of bug bug 179616
  11. Test updates from platform runtime other Eclipse SDK features on reference platforms and VMS