[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Graduation of Prosyst contributed bundles

Prosyst would like to graduate all of the listed bundles because:
- all of them, except for the util bundle, are implementations of OSGi
services. Perhaps sooner or later the community might need them
- we will support these bundles in the Equinox-Bundles component

Concerning your comment about the public API in the util bundle I suggest we
continue the discussion in the bug you have opened.


----- Original Message ----- 
From: Thomas Watson
To: equinox-dev@xxxxxxxxxxx
Sent: Monday, October 15, 2007 5:21 PM
Subject: [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:


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

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
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.


equinox-dev mailing list