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 Minutes - 20070327"
(→March 27, 2007) |
|||
| Line 11: | Line 11: | ||
===End of game=== | ===End of game=== | ||
| − | We are now entering M7. We are closing down. Who is going to go through all the open bugs to see if anything major slipped? | + | We are now entering M7. We are closing down. Who is going to go through all the open bugs to see if anything major slipped? |
| + | |||
| + | ===New Features=== | ||
| + | We have passed 3.3 M6 (the API freeze) and now are into the 3.3 M7 cycle. If we plan on doing any new feature work we must clear this with the PMC first. We should discuss any potential new features that we want to include for 3.3. | ||
[[Category:Equinox|Minutes - March 27, 2007]] | [[Category:Equinox|Minutes - March 27, 2007]] | ||
Revision as of 10:32, 27 March 2007
Contents
March 27, 2007
Conference Summary
Jeff was at The Server Side conference in Las Vegas last week and will let us know how the trip went.
Performance
A performance dynamic team will be constructed this milestone. We need to review where we are w.r.t. performance.
Logging
What is the replacement for Plugin.getLog().log(IStatus) or Platform.getLog()for people who want to get off core.runtime? Should there be an API equivalent of RuntimeLog that we have currently in equinox.common? For many bundles, the logging story needs to work both within a running OSGi instance and in standalone applicaitons
End of game
We are now entering M7. We are closing down. Who is going to go through all the open bugs to see if anything major slipped?
New Features
We have passed 3.3 M6 (the API freeze) and now are into the 3.3 M7 cycle. If we plan on doing any new feature work we must clear this with the PMC first. We should discuss any potential new features that we want to include for 3.3.