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 "Equinox p2 UI Plan"
(→M6 - Mar 12, 2009 - API Freeze) |
(→3.5 Milestone Plan) |
||
Line 18: | Line 18: | ||
* Layout glitches (Linux only) | * Layout glitches (Linux only) | ||
− | ==3.5 Milestone | + | ==3.5 Milestone Plans== |
+ | === M5 - Jan 30, 2009 - Major Feature Freeze === | ||
+ | *UI/Usability | ||
+ | ** improved error reporting and explanation of problems between the planner and the UI [https://bugs.eclipse.org/bugs/show_bug.cgi?id=218055 Bug 218055] | ||
+ | ** better presentation of repositories | ||
+ | *** Need to do a better job of deciding which repos to look up against [https://bugs.eclipse.org/bugs/show_bug.cgi?id=234213 Bug 234213] | ||
+ | *** Access to sites from all workflows [https://bugs.eclipse.org/bugs/show_bug.cgi?id=250316 Bug 250316] | ||
+ | *** user repo naming (regression of UM function) [https://bugs.eclipse.org/bugs/show_bug.cgi?id=194224 Bug 194224] | ||
+ | *** improve presentation of enabled/disabled repositories [https://bugs.eclipse.org/bugs/show_bug.cgi?id=218534 Bug 218534] | ||
+ | *** discovery mechanisms | ||
+ | ** Complete implementation for available view affordances [https://bugs.eclipse.org/bugs/show_bug.cgi?id=216032 Bug 216032] | ||
+ | ** Revert UI improvements | ||
+ | *** history view integrated into about dialog [http://wiki.eclipse.org/Equinox_p2_UI_3.5_workflows#About] | ||
+ | *** background job/progress reporting/UI freeze issues | ||
+ | ** investigate streamlined license UI [https://bugs.eclipse.org/bugs/show_bug.cgi?id=217944 Bug 217944] | ||
+ | ** Investigate the separation of product base vs. "add-ons" [https://bugs.eclipse.org/bugs/show_bug.cgi?id=215398 Bug 215398] | ||
+ | ** Investigate fast-path install scenarios [https://bugs.eclipse.org/bugs/show_bug.cgi?id=223264 Bug 223264] | ||
+ | *API | ||
+ | ** product configures user access to repos [https://bugs.eclipse.org/bugs/show_bug.cgi?id=231039 Bug 231039] | ||
+ | ** should UI be the one coordinating provisioning operations vs. having scheduling rules [https://bugs.eclipse.org/bugs/show_bug.cgi?id=218216 Bug 218216] | ||
+ | |||
+ | === M6 - Mar 12, 2009 - API Freeze === | ||
+ | *API | ||
+ | ** convert actions to handlers for UI pluggability | ||
+ | ** javadoc, package.html, and API scrub | ||
+ | ** automated test cases for all API contracts | ||
+ | ** examples or work with clients to demonstrate/verify that we provide appropriate level of reuse | ||
+ | |||
+ | === M7 - May 1, 2009 - Development Freeze === | ||
+ | ==Past 3.5 Milestones== | ||
=== M1 - Aug 8, 2008 === | === M1 - Aug 8, 2008 === | ||
* UI/Usability | * UI/Usability | ||
Line 67: | Line 96: | ||
** [[Image:Progress.gif]] Ability to reassemble groups (available, installed, history, repo management) into new locations (pref page vs. wizard, etc.) | ** [[Image:Progress.gif]] Ability to reassemble groups (available, installed, history, repo management) into new locations (pref page vs. wizard, etc.) | ||
− | + | == Items not yet assigned to milestones == | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | === UI/Usability === | |
* ability to install/uninstall user-named groups of IU's | * ability to install/uninstall user-named groups of IU's | ||
− | + | === API=== | |
* Investigate other levels of detail provided by API (listed from most general to most granular) | * Investigate other levels of detail provided by API (listed from most general to most granular) | ||
** One callable, preconfigured UI with pluggable policy (query providers, policies, etc.) | ** One callable, preconfigured UI with pluggable policy (query providers, policies, etc.) |
Revision as of 14:44, 10 December 2008
Contents
This page describes the work planned for the next release (3.5) 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.4.x maintenance stream.
The overall p2 plan for 3.5 is located at Equinox_p2_Plan
The milestone plans for 3.4 have moved to Equinox p2 UI Eclipse 3.4 Plan
Issues for 3.4.1
- Improved progress reporting and honoring cancellation requests
- Improved presentation of errors (resizability, formatting)
- Fix confusing restart language
- Annoying /low risk bugs
Issues for 3.4.2
- Enable a site when a user adds a disabled one (workaround until core fixes in 3.5)
- NLS formatting fixes
- Layout glitches (Linux only)
3.5 Milestone Plans
M5 - Jan 30, 2009 - Major Feature Freeze
- UI/Usability
- improved error reporting and explanation of problems between the planner and the UI Bug 218055
- better presentation of repositories
- Need to do a better job of deciding which repos to look up against Bug 234213
- Access to sites from all workflows Bug 250316
- user repo naming (regression of UM function) Bug 194224
- improve presentation of enabled/disabled repositories Bug 218534
- discovery mechanisms
- Complete implementation for available view affordances Bug 216032
- Revert UI improvements
- history view integrated into about dialog [1]
- background job/progress reporting/UI freeze issues
- investigate streamlined license UI Bug 217944
- Investigate the separation of product base vs. "add-ons" Bug 215398
- Investigate fast-path install scenarios Bug 223264
- API
- product configures user access to repos Bug 231039
- should UI be the one coordinating provisioning operations vs. having scheduling rules Bug 218216
M6 - Mar 12, 2009 - API Freeze
- API
- convert actions to handlers for UI pluggability
- javadoc, package.html, and API scrub
- automated test cases for all API contracts
- examples or work with clients to demonstrate/verify that we provide appropriate level of reuse
M7 - May 1, 2009 - Development Freeze
Past 3.5 Milestones
M1 - Aug 8, 2008
- UI/Usability
M2 - Sep 19, 2008
- UI/Usability
- Performance/Stability
- revisit checkbox/filter/deferred fetch strategy Bug 233269 (continuing in M3)
- investigate resolution in the background Bug 236495 (continuing in the scope of new workflows in M3)
M3 - Oct 31, 2008
- UI/Usability
- Complete new workflows (installed view may not yet be integrated with about dialog)
- Begin improved implementation of installed view Bug 224472
- Allow drill-down in installed view of requirements that are visible as groups
- Identify any necessary metadata changes to make this simpler/better (see Bug 227675)
- Performance/Stability
- finalize checkbox/filter/deferred fetch strategy Bug 233269
- resolution in the background to be provided as part of new workflows Bug 236495
- Investigate repo adding/loading performance issues and identify necessary changes to core Bug 236485
M4 - Dec 12, 2008
- UI/Usability
- Finish up installed view changes
- Complete integration of installed view with about dialog
- Install drill-down info also shown in install/update wizards Bug 250862
- Investigate the ability to provide optional/related content Bug 247342. (Decision is not to do anything at this time)
- Investigate better affordances in available view to show already installed, available updates, etc. Bug 216032
- Complete initial model/collector work needed to distinguish status and improve "already installed" filtering Bug 210583 and Bug 232632
- Finish up installed view changes
- Performance/Stability
- finalize checkbox/filter/deferred fetch strategy Bug 233269
- Usability+Performance
- More selective loading of repos when sites are added Bug 236485
- API
- Separation of contributions from the rest of the code Bug 221760
- Ability to reassemble groups (available, installed, history, repo management) into new locations (pref page vs. wizard, etc.)
Items not yet assigned to milestones
UI/Usability
- ability to install/uninstall user-named groups of IU's
API
- Investigate other levels of detail provided by API (listed from most general to most granular)
- One callable, preconfigured UI with pluggable policy (query providers, policies, etc.)
- Expose all building blocks for RCP apps
- Individual wizards, dialogs, actions
- Content and label providers
- Ensure code is structured for managed scenarios (minimal UI that is required)
- Silent/automatic updating, user never sees the update UI, it just happens (but may need confirmation, restart dialog, etc.)
- User's environment is defined explicitly by someone external (administrator)
- Upgrade or install to a new specification
- Compare current installation to required one