Community
Participate
Working Groups
This is an umbrella bug for the ongoing work to implement the upcoming OSGi R8 Core Framework specification. The date has not been set for when this specification will be released. Equinox will continue to provide the reference implementation for the core Framework specification for the R8 release. Ongoing work is being done in the osgiR8 branch: https://git.eclipse.org/c/equinox/rt.equinox.framework.git/log/?h=osgiR8
Tom, do you plan to merge these for M3?
(In reply to Alexander Kurtakov from comment #2) > Tom, do you plan to merge these for M3? No, but this is a plan item for which we cannot change the milestone (without messing up the plan documented by Dani). At the end of this release I will close this plan item and open a new one for 4.17 to track the ongoing work.
(In reply to Thomas Watson from comment #3) > (In reply to Alexander Kurtakov from comment #2) > > Tom, do you plan to merge these for M3? > > No, but this is a plan item for which we cannot change the milestone > (without messing up the plan documented by Dani). At the end of this > release I will close this plan item and open a new one for 4.17 to track the > ongoing work. No, you cannot close it. As it was not delivered it needs to remain open and point to the 4.17 item.
(In reply to Dani Megert from comment #4) > (In reply to Thomas Watson from comment #3) > > (In reply to Alexander Kurtakov from comment #2) > > > Tom, do you plan to merge these for M3? > > > > No, but this is a plan item for which we cannot change the milestone > > (without messing up the plan documented by Dani). At the end of this > > release I will close this plan item and open a new one for 4.17 to track the > > ongoing work. > No, you cannot close it. As it was not delivered it needs to remain open and > point to the 4.17 item. I find it strange to leave a plan item open for a past release. Especially a plan item like this that was only meant to track progress of the ongoing development (OSGi R8 in this case) being done in a topic branch osgiR8 and was not meant to be merged into master for the targeted release. But I will do as you ask :)
(In reply to Thomas Watson from comment #5) > (In reply to Dani Megert from comment #4) > > (In reply to Thomas Watson from comment #3) > > > (In reply to Alexander Kurtakov from comment #2) > > > > Tom, do you plan to merge these for M3? > > > > > > No, but this is a plan item for which we cannot change the milestone > > > (without messing up the plan documented by Dani). At the end of this > > > release I will close this plan item and open a new one for 4.17 to track the > > > ongoing work. > > No, you cannot close it. As it was not delivered it needs to remain open and > > point to the 4.17 item. > > I find it strange to leave a plan item open for a past release. Especially > a plan item like this that was only meant to track progress of the ongoing > development (OSGi R8 in this case) being done in a topic branch osgiR8 and > was not meant to be merged into master for the targeted release. > > But I will do as you ask :) The 'plan' bug queries are part of our plans. If we move 'plan' bugs it destroys that plan as one cannot see what was delivered and what was not delivered.
Tom, can we close this one now?
(In reply to Alexander Kurtakov from comment #7) > Tom, can we close this one now? Yes, note that R8 was not merged to master for the 4.16 release. That is planned for 4.17.
