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.
Difference between revisions of "Equinox/p2/Helios/Plan"
(→3.6 items left) |
|||
| Line 33: | Line 33: | ||
* Release train build/repository assistance | * Release train build/repository assistance | ||
| − | === | + | === Helios items left === |
(Note this list is currently just the remaining items from the 3.5 plan. This list needs reviewing as some items are likely already done) | (Note this list is currently just the remaining items from the 3.5 plan. This list needs reviewing as some items are likely already done) | ||
Revision as of 14:19, 27 July 2009
This page lays out milestone plans for the development of Equinox p2 in the Eclipse Helios release (aka the Eclipse Platform version 3.6).
- For a high level feature plan, see Equinox/p2/Galileo/Features.
- For a more detailed view of the UI plan, see Equinox p2 UI Plan.
Contents
Current Plan: M1- August 7, 2009
- Decompression
- Bug triage, community assistance
- Critical bug fixes
- Galileo SR1 (3.5.1) fixes
Future Plans
M2 - September 18th, 2009
- Planning
- Galileo SR1 (3.5.1) fixes
M3 - October 30, 2009
M4 - December 11th, 2009
M5 - January 29th, 2010 - Major Feature Freeze
M6 - March 12th, 2010 - API Freeze
M7 - April 30, 2010 - Feature Freeze
- Polish items
- Performance work
- UI Accessibility
- Testing and test framework improvements
- Release train build/repository assistance
Helios items left
(Note this list is currently just the remaining items from the 3.5 plan. This list needs reviewing as some items are likely already done)
- Transport
- Better explanation of errors [1]
- Artifact repository
- Robustness in reading and writing.
- Mirroring application... ppl still have problems
- Concurrency issues when reading and writing (one process)
- Eclipse touchpoint
- Improve detection for conflicting arguments
- Native touchpoint
- Improve detection for conflicting arguments
- Engine
- Reacting to change of property
- GC of profile registry
- Update manager
- Provide replacement constructs for UM
- Review problems connecting to legacy update sites
- Publisher / generator
- Get rid of the generator bundle to the benefit of the publisher
- Director application
- Make it easier to do a set of operations (do we need a "response file")
- Provide the ability to set properties at install time
- Mirror app
- Need to make the artifact repository more robust
- UI
- Ability to define/install/uninstall user-named groups of IU's
- Fast-path install scenarios (gestures for auto-install)
- Show licenses by license instead of by IU
- Showing non-greedy optional dependencies for selection
Previous Plans
Past Releases
Legend
Needs some investigation
Work in progress
Bug fixed / Feature added