| Summary: | [plan] OSGi standards participation | ||
|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | DJ Houghton <dj.houghton> |
| Component: | Framework | Assignee: | equinox.framework-inbox <equinox.framework-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P4 | CC: | bpasero, caniszczyk, eclipse, Konstantin.Scheglov, martin.gutschelhofer, mike.milinkovich, mkwong, pascal, tjwatson |
| Version: | 3.3 | Keywords: | plan |
| Target Milestone: | 3.4 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
DJ Houghton
The current thinking is that we may *not* want to do future (OSGi R5) work directly in HEAD for the 3.4 release. The reason is the next major OSGi spec release (R5) is not likely to go public until a while after the 3.4 release. It is likely that we will start an incubator workarea in equinox to prototype R5 work for at least the Framework. I see no reason to destabilize 3.4 unless we have strong requirements for a new feature from the future OSGi specification. Even then we should be able to selectively implement what we need in that (unlikely) case. Moving to 3.5. The plan is to have a final OSGi spec some time in 1Q 2009. Our goal is to have 3.5 be the first implementation of Equinox to support the next rev of the OSGi spec. Moving back to 3.4. The Equinox team has had ongoing participation in OSGi specification process and continues to monitor the OSGi specification process. For the Eclipse 3.4 release OSGi did not have a major specification release. There were a number of clarifications made to the OSGi R4.1 specification that have been verified and corrected (if necessary) in Eclipse 3.4 |