| [equinox-dev] Graduation of Prosyst contributed bundles |
The bundles contributed by Prosyst have been in the incubator since July. The codebase Prosyst donated is already production quality and has been used in many products at Prosyst. A small number of issues have been reported against the bundles in the incubator. But these are to be expected and the committers from Prosyst have been responsive in addressing the issues. At this point I would like to ask Prosyst which of the incubator bundles would they like to graduate and support in the Equinox-Bundles component?
We have the following bundles to consider:
org.eclipse.equinox.util (https://bugs.eclipse.org/bugs/show_bug.cgi?id=181731)
org.eclipse.equinox.ds (https://bugs.eclipse.org/bugs/show_bug.cgi?id=181733)
org.eclipse.equinox.ip (https://bugs.eclipse.org/bugs/show_bug.cgi?id=181734)
org.eclipse.equinox.wireadmin (https://bugs.eclipse.org/bugs/show_bug.cgi?id=181736)
org.eclipse.equinox.io (https://bugs.eclipse.org/bugs/show_bug.cgi?id=181737)
The last four bundles (ds, ip, wireadmin, io) all provide implementations to OSGi specifications and do not provide public API. I am concerned about the amount of public API in the org.eclipse.equinox.util bundle (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=206151).
We should consider the following when making this decision:
1) Which bundles does the community need? We do not need to graduate all the bundles if we determine that the community is not interested in all of them.
2) Which bundles do we have sufficient resources to support at the graduated level.
3) How much API will be graduated. Graduated API has a long term commitment and requires a lot of review and must be positioned such that we do not break compatibility while evolving the API after graduation.
Tom