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.
Equinox p2 UI Plan
Revision as of 14:29, 24 June 2009 by Unnamed Poltroon (Talk)
Contents
This page describes the work planned for the next release (3.6) of the p2 UI. This includes improvements for the p2 UI in the Eclipse SDK, as well as issues that have to be addressed for alternate UIs (such as RCP app requirements). Important fixes will be examined for inclusion/backport to 3.5.x maintenance stream.
The overall p2 plan for 3.6 is located at Equinox_p2_Plan
The milestone plans for 3.5 have moved to Equinox p2 UI Eclipse 3.5 Plan
The milestone plans for 3.4 have moved to Equinox p2 UI Eclipse 3.4 Plan
3.6 Ideas list
UI/Usability
- Ability to install/uninstall user-named groups of IU's
- Separation of product base vs. "add-ons" Bug 215398
- Fast-path install scenarios Bug 223264
Major Features
- User's environment is defined explicitly by someone external (administrator)
- Upgrade or install to a new specification
- Compare current installation to required one
API
- Core/UI responsibilities
- should UI be the one coordinating provisioning operations vs. having scheduling rules Bug 218216
- batched repo events
- Supported API for all UI building blocks
- Individual wizards, dialogs, commands
- consider handlers vs. actions for UI pluggability/are some command ID's contracts (so clients can invoke UI by id)
- Content and label providers
3.6 Milestone Plans
M1 - (date?)
-
alternate license UI Bug 217944 - <Susan>
