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 "PDE/Plan/3.7"
(→Schedule) |
(→M6 - March 11 (API Freeze)) |
||
| Line 68: | Line 68: | ||
=== M6 - March 11 (API Freeze) === | === M6 - March 11 (API Freeze) === | ||
| + | |||
| + | {{PlanItem|Polish||Investigate}} | ||
| + | {{PlanItem|Performance||Investigate}} | ||
| + | {{PlanItem|Bug fixing||Investigate}} | ||
| + | |||
=== M7 - April 29 (Feature Freeze) === | === M7 - April 29 (Feature Freeze) === | ||
=== RC Builds === | === RC Builds === | ||
Revision as of 12:06, 16 August 2010
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
Planned Items
The following items are being considered for 3.7, but have not been scheduled into a specific milestone
API Tools
No input required:
Support API compatibility checks against unresolved bundles (271045)
Support include lists for API tools ant tasks (270973)
Support installation resolution for API tools tasks (322572)
Useful before Christmas:
Integrate API use reports into the IDE and workspace build (310547)
Support to filter references from an API use report (271044)
Consumer based API use report (322571)
Report delta between two API use reports (266903)
PDE UI
No input required:
Support bundle import from the package explorer (313392)
Properly import projects with a different name when project already exists in the workspace (310495)
Support to edit properties for .products (260328)
JDT is providing a patch:
Anonymous workspace for JUnit Plug-in Tests (127719)
Start early:
API for bundle importers and bundle import wizard pages (320552)
Avoid resolution of p2 based targets when contents cached locally (276326)
Schedule
Dates are listed in the Eclipse Platform Releng Calendar (view as iCal). Note that some work items will take longer than one milestone to complete. Plan items are listed in the milestone when work is intended to start on the item. The plan is intentionally heavy on milestones two through five to allow for bug fixing, iterative development, performance and polish work in later milestones.
M1 - August 6
No Major Work Items
M2 - September 17
Prepare 3.6.1 Fixes
Create 3.7 Plan
Improve state initialization (312495)
Support include lists for API tools ant tasks (270973)
Support installation resolution for API tools tasks (322572)
Support to edit properties for .products (260328)
Avoid resolution of p2 based targets when contents cached locally (276326)
M3 - October 29
API for bundle importers and bundle import wizard pages (320552)
Support bundle import from the package explorer (313392)
Properly import projects with a different name when project already exists in the workspace (310495)
Integrate API use reports into the IDE and workspace build (310547)
Consumer based API use report (322571)
M4 - December 10
Support to filter references from an API use report (271044)
Report delta between two API use reports (266903)
M5 - January 28
Prepare 3.6.2 Fixes
Support API compatibility checks against unresolved bundles (271045)
M6 - March 11 (API Freeze)
Polish
Performance
Bug fixing
M7 - April 29 (Feature Freeze)
RC Builds
Update Copyrights
Check for Broken NLS
Doc Pass
Bug fixing
Overall Goals
This section will list general goals for the 3.7 release using information from the Retrospective.
- Code Quality - Review patches more carefully, write tests for new code, review risky fixes
- Stability - Safe incremental improvements over one-off feature work
Unplanned Items
This section will list items that we are interested in completing during 3.7 but have not been scheduled. For general ideas, use the Wishlist.
Redo all performance tests