For developers, same as always, put "PMC" in status whiteboard and add "jlanuti@us.ibm.com" as CC.

For PMC, instead of using a "+1" comment, you update the "pmc_approved" flag for your email address with a "+" for approve and a "-" for reject. Once the developer puts a bug in "PMC", I will add your bugzilla flags as a "?", which will generate you a handy email, requesting you to approve the bug. Once the appropriate amount of approvals is garnered, I will update the status whiteboard to "PMC_approved" or if need be, to "PMC_rejected". The PMC pages are updated to ONLY look at the flags and not text comments.

WTP 1.5.4

WTP 1.5.5

Scope

WTP 1.5.5 is a service release for critical defects, regressions, and adopter issues only. There should be no translation or UI changes, nor should it affect any API reported through the adopter scanning tools.

Bug Approval

All bugs must be approved by the normal PMC Approval Process.

Timeline

The proposal is that to keep focus on WTP 2.0 shutdown, we don't actually start development until the end of June and don't declare an M build until July 13th. Then, we take the biweekly approach we did in 1.5.4, with a few RC shutdown weeks leading to an August 31 GA. RDB will work throughout May and June since they don't have any 2.0 work and are preparing migration efforts to DTP.

Ensure all plugin manifests have execution environments specified - David to open bugzilla, each component needs to do this for RC0.

Use signed plugin jars - This is not a requirement anymore, are we still going to do for WTP 2.0?

Each component must run the eclipse copyright tool to ensure all files have a proper copyright. JSF? J2EE? Server tools?

Component Leads - Please update the exception section of the WTP 2.0 Europa Ramp Down Plan with the relevant info and bugzilla numbers for exceptions to M6 feature complete.

April 6th - May 18th, WTP RC0

April 2007 - May 2007

Monday

Tuesday

Wednesday

Thursday

Friday

14 Function and Compatibility Tests

15 Defect Verifications Mustfix defects

16 Defect Verifications Mustfix defects

17 Defect Verifications Status Call Thumbs Up Test

18 Declare WTP 2.0 RC0

Build Status

EMF and GEF M7 will be declared this week.

Upgraded Xerces from 2.8 to 2.9. Any issues? Tested?

Please smoke test and update wiki to declare RCO I Build.

JUnits?

Function and Compatibility Tests

Please plan to take a step back and run some regression tests on any changed areas and function tests on any approved new function. Also, remember to work on closing out bug verifications.

RC0 New and Noteworthy - See Nitin's note for more information.

API Violations Review - Cannot underestimate the importance of this in the stability and quality of WTP as a platform. These numbers are embarrassingly high. Each component needs to really get someone focused each week on improving these numbers and opening API requests.

Action 1 = For any violation, open a bug to request API or fix code to not use internal discouraged access. An example is using images or labels from other plugins, these should be copied into your plugin. Also, using internal classes instead of the API interfaces.

Action 2 = If you do have a clean plugin of API violations/discourage access, switch prereq ranges wide so you can react to small version number changes without issue.

Action 3 = To be able to develop with discouraged access enabled, we need to update plugin's .classpath rules. Should we turn off defaults to expose all warnings to get a quicker resolution?