View source for WTP 3.2 Ramp down Plan for Helios

== WTP Ramp down for Helios== 

For reference, see the [[Helios/Simultaneous_Release_Plan| Helios Simultaneous Release Plan]],
in particular the [[Helios/Simultaneous_Release_Plan#Milestones_and_Release_Candidates | Milestones and Release Candidates]].

=== Early Milestones ===

Just to remind everyone, there is a "ramp down" for every milestone. Typically the
last week of a Milestone is for testing, and fixing only regressions and P1 or blocking defects. For
milestones, during that final week, the Project lead (or delegate) is enough to review and approve a bug for inclusion in that milestone. Such "final week" bugs, should be formally marked for review and approved before releasing or requesting a respin. 

=== M5: The EclipseCon Milestone ===

We plan to ensure good enough quality that M5 can be used by EclipseCon presenters for presentations, demos, and tutorials.

=== M6: Feature Complete, API Freeze, UI Freeze ===

For M6, we plan to be functionally and API complete and the remaining Milestone and Release Candidates
are for (only) fixing bugs, or fixing release required items (such as version numbers, licensing, etc.).

From M6 to M7, we expect each component lead (or delegate) to review and verify their teams' bugs (i.e.
no PMC review ... though we will be watching :) ).

We expect committers to concentrate on performance and other "internal" improvements, after M6, leading
up to M7. In addition, it's a good time to improve documentation (for end-users and adopters).

If there are exceptions to these conditions, then they will require PMC review. In that event, the
Project Lead must open a bugzilla, detailing the feature to be added after M6 and mark for PMC review.
And that must be done before M6 is declared. Exceptions (with bug numbers) will also be listed at the
end of this document, to help facilitate communication.

:*Place [NLS] or [API] or [Feature] in the heading of the bug depending on which type it is
:*Notify PMC members [http://wiki.eclipse.org/index.php/WTP_PMC_Defect_Review PMC Defect Review], 1 vote is needed
:*Once approved, code can be released
:*Update this page to append the bug at the bottom of the page, so adopters have a central place to find exceptions they may have to react to: re-translate, generate new screen captures, modify their own documentation, or adjust testing procedures.

=== M7: PMC Review starts after M7 ===

After the M7, the process of building and testing Release Candidates begins (sometimes called "the end
game"). At first, after M7 but before RC1, in addition to the normal component team review, at least 1
PMC member must also review and vote +1 after reviewing the bug for appropriateness (weighing benefits
and risks).

=== Release Candidates ===

We expect Release Candidates to truly be candidates for release (i.e. well performing, high quality,
product ready code).  After the first RC is produced, other RCs will be produced, as needed, every week.

After M7 is produced, the time for general functional improvements is long past. The following describes the types of bugs that would be appropriate: 
<ol>
* A regression
* A P1 or P2 bug, one that is 'blocking' or 'critical', and some cases of 'major' severity. 
* Documentation and PII files are exceptions to the normal PMC required review, since there is little chance of that breaking anything, though it is still expected to be complete by M6, and remaining work to be only documentation fixes (that is, no refactoring of plugins, build changes, etc, without PMC review and approval). 
* In addition to a bug meeting the above priority/severity conditions, there should be a simple, safe, well understood fix that is well isolated from effecting other components, that doesn't affect API or adopters, that has been well reviewed and well tested. 
* As each Release Candidate passes, the criteria for weighing the benefit-to-risk ratio criteria gets higher and higher, and as such requires a larger number of PMC members to review.
</ol>

==== RC1 ====

After RC1, same rules as after M7: besides the normal component team review, at least 1 PMC members must also review and vote +1 after reviewing the bug for appropriateness and risk.

==== RC2 ====

After RC2, besides the normal component team review, at least 2 PMC members must also review and vote +1 after reviewing the bug for appropriateness and risk.

==== RC3 ====

After RC3, besides the normal component team review, at least 3 PMC members must also review and vote +1 after reviewing the bug for appropriateness and risk.

==== RC4 ====

After RC4 is produced, we'll prepare and test the zip's, update site, web pages, etc.

=== Release ===

Celebrate!

== Post-M6 Exceptions by sub-project ==

===Common===

[https://bugs.eclipse.org/bugs/show_bug.cgi?id=273161 273161] [UI] Validation Framework UI not completely accessible

[https://bugs.eclipse.org/bugs/show_bug.cgi?id=306534 306534] [API] Child modules are ignored for modules with a single root

[https://bugs.eclipse.org/bugs/show_bug.cgi?id=308098 308098] [UI] Project default location usability

===Server Tools===
[https://bugs.eclipse.org/bugs/show_bug.cgi?id=308916 308916] [UI] Add Tomcat 7 support to WTP ServerTools

[https://bugs.eclipse.org/bugs/show_bug.cgi?id=309020 309020] [UI] Server initialization may hang the UI thread

===Java EE Tools===

[https://bugs.eclipse.org/bugs/show_bug.cgi?id=306420 306420] [NLS] We must use Java EE, not JEE, in our UI

[https://bugs.eclipse.org/bugs/show_bug.cgi?id=307148 307148] [UI] [API] Wrapper bug for j2ee assembly page

[https://bugs.eclipse.org/bugs/show_bug.cgi?id=304654 304654] [UI] [API] Proposal for EAR module assembly prop page enhancement

[https://bugs.eclipse.org/bugs/show_bug.cgi?id=303600 303600] [UI] Missing UI, cannot add classpath dependencies anymore

[https://bugs.eclipse.org/bugs/show_bug.cgi?id=305650 305650] [UI] No UI for some variable-reference functionality

[https://bugs.eclipse.org/bugs/show_bug.cgi?id=305971 305971] [https://bugs.eclipse.org/bugs/show_bug.cgi?id=306174 306174]  [UI] Somewhat duplicate issues regarding UI for manifest entries, a UI which existed only for 2 weeks and was found to need substantial redesign. 

[https://bugs.eclipse.org/bugs/show_bug.cgi?id=307766 307766] [UI] Updating web fragment module overlay icon

[https://bugs.eclipse.org/bugs/show_bug.cgi?id=307931 307931] [API] Binary WebFragment support

[https://bugs.eclipse.org/bugs/show_bug.cgi?id=306689 306689] [UI] Incorrect names displayed in "modules" section of Project Explorer

[https://bugs.eclipse.org/bugs/show_bug.cgi?id=307183 307183] [API] Invalid dynamic reference created when jar dropped into lib dir

[https://bugs.eclipse.org/bugs/show_bug.cgi?id=308103 308103] [UI] finalPerspective for Static Web projects should be Web perspective

[https://bugs.eclipse.org/bugs/show_bug.cgi?id=308282 308282] [UI]Additional changes to Module assembly

=== JSF ===

[https://bugs.eclipse.org/bugs/show_bug.cgi?id=299813 299813] [JSF2.0] new Implicit Objects defined for use in EL expressions 

[https://bugs.eclipse.org/bugs/show_bug.cgi?id=299781 299781] [JSF2.0] Contribute ContentModel for standard JSF2 taglibs 

[https://bugs.eclipse.org/bugs/show_bug.cgi?id=295246 295246] [JSF2.0] FacesConfig model update [[Image:Tick.gif]]

[https://bugs.eclipse.org/bugs/show_bug.cgi?id=299784 299784] [JSF2.0] Contribute ContentModel for "in project" composite components 

[https://bugs.eclipse.org/bugs/show_bug.cgi?id=299780 299780] [JSF2.0] create meta-data for new taglibs 

[https://bugs.eclipse.org/bugs/show_bug.cgi?id=295514 295514] [JSF2.0] create content types for Facelets 

[https://bugs.eclipse.org/bugs/show_bug.cgi?id=306308 306308] [JSF2.0] WPE-Properties View-Attributes tab should show all attributes of a tag in an XHTML page [[Image:Tick.gif]]

<strike>[https://bugs.eclipse.org/bugs/show_bug.cgi?id=305210 305210] Refactor JSF plugins for easier adoption </strike>

[https://bugs.eclipse.org/bugs/show_bug.cgi?id=306426 306426] [JSF 2.0] Support for Resource Loading facility

[https://bugs.eclipse.org/bugs/show_bug.cgi?id=306458 306458] Make Services Factory Configurable

===JSDT===
[http://bugs.eclipse.org/274550 274550] [UI][Feature] Clean up and streamline explorer UI

[http://bugs.eclipse.org/298240 298240] [UI][Feature] provide the ability to view all scripts currently loaded 

[http://bugs.eclipse.org/305913 305913] [UI][Feature] Make use of SSE Content Assistance Cycling


===JPT===
[https://bugs.eclipse.org/bugs/show_bug.cgi?id=296503 296503] Support invocation of EclipseLink and JAXB RI schema generators

[https://bugs.eclipse.org/bugs/show_bug.cgi?id=309482 309482] JoinFetch support on Eclipselink element collection mappings

<!--
===Server===
-->

===Source Editing===
[http://bugs.eclipse.org/256339 256339] [UI][Feature] Migrate XSL Syntax Highlighting to Semantic Highlighting 

[http://bugs.eclipse.org/266683 266683] [UI][Feature] Provide a global CMDocument cache

[http://bugs.eclipse.org/304145 304145] [UI][Feature] Make use of New Content Assistance Cycling

[http://bugs.eclipse.org/304620 304620] [UI] Markup Validator should be run along with the XML Validator

[http://bugs.eclipse.org/305339 305339] [NLS] JSPTranslatorPersister should be updated to use a job

<!--
===Web Services===


===Releng===

*Repackage capabilities plugins

*Provide 4 "product packages" (JavaScript, XML, Web Development, Java EE Development)

===Dali===

*Support for Entities in JARs [https://bugs.eclipse.org/bugs/show_bug.cgi?id=197069 197069]
*Added provisional API as part of a bug fix [https://bugs.eclipse.org/bugs/show_bug.cgi?id=269256 269256]
*Fix API leakage [https://bugs.eclipse.org/bugs/show_bug.cgi?id=269581 269581]

===Server Tools===
* Support for multiple Server profilers [https://bugs.eclipse.org/bugs/show_bug.cgi?id=270503 270503]

-->

[[Category:Eclipse Web Tools Platform Project]]