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 "Eclipse4/SR1Plan"
(New page: == Eclipse 4.2 SR1 Plan == The goal is to plan out what we can do for SR1. We should be trying to limit the amount of work that we commit to here because there's only a short time in whic...) |
(→Deliverables) |
||
| Line 5: | Line 5: | ||
=== Deliverables === | === Deliverables === | ||
| − | + | === Bug fixes === | |
We should go over the current list of defects and make sure that we're only attempting to address significant defects. Also we should expect that we will be receiving some good ones from the community that we'll have to address | We should go over the current list of defects and make sure that we're only attempting to address significant defects. Also we should expect that we will be receiving some good ones from the community that we'll have to address | ||
The work for making sure that BiDi and accessibility are OK go into this bucket but are non-negotiable in the sense that this work has already been committed to. | The work for making sure that BiDi and accessibility are OK go into this bucket but are non-negotiable in the sense that this work has already been committed to. | ||
| − | + | === Formal API specifications === | |
| + | |||
| + | This breaks down into 3 basic areas; UI Model, DI and Services as well as two main activities that have to be done for each area; documentation and refactoring. | ||
| + | |||
| + | The first pass should be to define the scope of the API so that we spend our time documenting and refactoring only those things that we are sure should be API (note that we can likely defer things that are on the fence as 'provisional', giving us the 4.3 cycle to finalize their status). | ||
| + | |||
| + | ==== UI Model Documentation ==== | ||
| + | |||
| + | ==== DI Documentation ==== | ||
| + | |||
| + | ==== Services Documentation ==== | ||
Revision as of 09:56, 6 June 2012
Contents
Eclipse 4.2 SR1 Plan
The goal is to plan out what we can do for SR1. We should be trying to limit the amount of work that we commit to here because there's only a short time in which to work and we have to take into account that it's summer and many of us will be taking vacation and / or will only be working 4 days / week for July.
Deliverables
Bug fixes
We should go over the current list of defects and make sure that we're only attempting to address significant defects. Also we should expect that we will be receiving some good ones from the community that we'll have to address The work for making sure that BiDi and accessibility are OK go into this bucket but are non-negotiable in the sense that this work has already been committed to.
Formal API specifications
This breaks down into 3 basic areas; UI Model, DI and Services as well as two main activities that have to be done for each area; documentation and refactoring.
The first pass should be to define the scope of the API so that we spend our time documenting and refactoring only those things that we are sure should be API (note that we can likely defer things that are on the fence as 'provisional', giving us the 4.3 cycle to finalize their status).