Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Equinox p2 UI Plan
Revision as of 15:07, 21 February 2008 by Susan franklin.us.ibm.com (Talk | contribs)
Contents
At this stage in the 3.4 release, we are prioritizing the remaining work items for the 3.4 delivery.
Remaining priorities
P0 = must have before turning the p2 switch on in the SDK P1 = must have for 3.4 release P2 = should have for 3.4 - makes UI more usable P3 = nice to have for 3.4 - "wow factor"
- Repo login and user verification issues <Tim>
- Recovery application <Tim>
- Integrate artifact GC and any prefs needed <Susan>
- Additional context and views shown in available and installed IU views <Susan>
- Streamlined revert UI/history page <Susan>
Milestone plans
M6
- P0 Understand the tie between the UI and the Update manager, UM hides its contributions if p2 is there <Tim>
- P0 Fix annoying auto-update popup bugs and overeager error reporting
- P0 Detect invalid update plans before notifying user
- P1 Verify trust and insert UI for signature verification <Tim>
- P1 Detection of install handlers and launch UM when found <Susan>
- P1 Ability to add repos by just pointing at a jar, dir that is not already a p2 repo (UM extension locations) <Susan>
- P1 Integration of directory watcher/drop-ins folder prefs <Susan>
M5
- P1 Performance issues
- Restructure available IU viewer for PDE consumption
- API for profile change requests
- Automatic updates life-cycle, affordance and popup workflow
- Improve property pages for IUs in end user UI
- Summary info for install/update wizards
M4
- Polish install and update scenarios
- Notify of auto-download separate from install
- Preferences for reminding user of available updates Bug 207493
- Performance/progress when resolving/planning
- Improved support for browsing repos
- IU categories Bug 203115
- remove duplicates, better sorting
- show only latest versions
- Refactoring and code polish items
- UI for Revert Bug 205223
- Improved way to present licenses and remember accepted licenses Bug 205232
- Admin UI features as needed by team
M3
- End user UI
- Improve workflow and information pre-<install/update/uninstall>
- Prompting replaced by informational wizard Bug 204321
- Size/time estimation on install/update (Depends on Bug 201488)
- One entry point per group Bug 204823
- Detect invalid states on install/update/uninstall
- Polling for software updates and associated user prefs
- Improve workflow and information pre-<install/update/uninstall>
- Admin UI
M2
- Install, Uninstall, and/or update IU's from running profile
- user views installed IU's in the current profile
- user can manage repositories as an advanced feature (separate button on dialog)
- repositories are colocated (no distinction between metadata and artifact repo)
- UI prequalifies the install
- figure out if the install is valid using oracle
- [deferred] use advanced oracle to flag any invalid states
- [deferred] use advanced oracle to precompute info such as download size/time, etc.
- user can uninstall an installed IU
- user can update an installed IU
- Repository naming
- repo level
- [deferred] user can override repo name
- Better filtering of repos and IU's (show only what's relevant to end user)
- Refactor drag support into common UI project
- Filtering of IU's based on entry point concept
- Give the ability to name what is being installed
- Admin UI can launch end user UI from selected profile in profile view
- should be able to disable colocated repo management
- AdminUI views show enhanced info about objects (multiple columns)
- AdminUI and User UI contribute different property pages
M1
- Browse repositories
- Add/remove repositories
- Browse IU's in a metadata repository
- Install IU from a metadata repository into a selected profile
- Browse profiles
- Add/remove profiles
- Browse IU's in a profile
- Uninstall IU
Additional Requirements
This is a list of some original UI requirements that are not on the 3.4 plan.
- Installation by drag and drop on a running eclipse
- Install from a click on the webpage
- Silent installation
- Support installation even when there are errors in the configuration