Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "PDE/Plan/3.6"
(→UI) |
|||
| Line 46: | Line 46: | ||
* {{bug|216037}}: [API] Way to modify MANIFEST files | * {{bug|216037}}: [API] Way to modify MANIFEST files | ||
| − | * {{bug|169340}}: [API] [target] Expose a means to programmatically set and load a Target Platform | + | * Target Platform |
| + | ** Continue target platform definition enhancements. Target platform/definition contents could be managed entirely with p2 profiles for improved performance and for proper persistence/restoration. As well, OSGi state could be associated with target definitions and leveraged for per-project target build paths. | ||
| + | ** {{bug|169340}}: [API] [target] Expose a means to programmatically set and load a Target Platform | ||
| + | ** {{bug|159072}}: [target] associate target definitions on a per-project basis (multiple target platforms per workspace) | ||
* {{bug|269573}}: [product] support more platforms in product files | * {{bug|269573}}: [product] support more platforms in product files | ||
* {{bug|260328}}: [product] add a way to specify properties | * {{bug|260328}}: [product] add a way to specify properties | ||
| − | + | ||
* {{bug|106676}}: [pde viz] Graduate | * {{bug|106676}}: [pde viz] Graduate | ||
* {{bug|142422}}: [refactoring] update class references in dependent plugins | * {{bug|142422}}: [refactoring] update class references in dependent plugins | ||
Revision as of 15:41, 8 July 2009
Note: This is an unofficial document used by the PDE team to help with the planning process. Items on this list aren't guaranteed to be found in a release.
Contents
Schedule
Dates are listed in the Eclipse Platform Releng Calendar (view as iCal)
Scope
TODO
Priorities
- PDE becomes BDE: more bundle, less plug-in
- Revamp the PDE webpage to be more welcoming
- Add missing Incubator projects such as Picasso to the webpage, and use Athena/Hudson to propose builds/update-sites of these projects
- More tests to improve code coverage
- Get more committers
- One mailing list (ie., just pde-dev, get rid of pde-build-dev and pde-ui-dev)?
Platforms
- Eclipse: 3.6
- Target Platforms back to 3.0 supported
- Java: J2SE 1.4 or later required
- Operating Systems: all supported by Eclipse
Ramp Down
TODO
Projects
API Tools
- bug 215073: [api tooling] Support for package versioning
- bug 255771: Report usage of non-available new code
Build
- bug 154083: Incremental Plug-in Build
- bug 106594: Make PDE fully workspace aware
- bug 222965: Use frameworkadmin to generate config.ini / eclipse.ini
UI
- bug 216037: [API] Way to modify MANIFEST files
- Target Platform
- Continue target platform definition enhancements. Target platform/definition contents could be managed entirely with p2 profiles for improved performance and for proper persistence/restoration. As well, OSGi state could be associated with target definitions and leveraged for per-project target build paths.
- bug 169340: [API] [target] Expose a means to programmatically set and load a Target Platform
- bug 159072: [target] associate target definitions on a per-project basis (multiple target platforms per workspace)
- bug 269573: [product] support more platforms in product files
- bug 260328: [product] add a way to specify properties
- bug 106676: [pde viz] Graduate
- bug 142422: [refactoring] update class references in dependent plugins
- bug 231099: [launching] Make launch config files more CVS-friendly
- bug 164188: Need tooling for access rules on vm packages
- bug 227055: [schema] allow for the definition of custom attribute types
- p2 publishing tooling (replace update site tooling)