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

Move WS bundles to orbit - Update?

Use signed plugin jars - This is not a requirement anymore, but we will still investigate.

Each component must run the eclipse copyright tool to ensure all files have a proper copyright. Update?

Component Leads - Take a look at the new New WTP 2.0 Plan document published by Raghu and make any updates for your component. The purpose is to have a good clear picture of what we achieved and what we wanted to acheive but deferred. Update?

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.

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?