|Re: Re: [equinox-dev] Graduation of Prosyst contributed bundles|
We should develop some of our own testcases to get complete coverage. The OSGi test suite can be used by the committers (which are also OSGi members) during our test pass for each mile stone. The OSGi test cases should not be considered as a complete test suite, in many cases they will let bugs slip by. Every bug we fix which the OSGi test suite did not catch should likely have an automated testcase created.
We have looked into running the OSGi TCK with each build during the junit tests, but the effort was high and in the end it was decided to run the OSGi TCK as part of our manual milestone test pass.
Pavlin Dobrev ---10/15/2007 10:11:11 AM---All of the bundles that implement OSGi defined services:
Pavlin Dobrev <p.dobrev@xxxxxxxxxxx>
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
10/15/2007 10:11 AM
Re: [equinox-dev] Graduation of Prosyst contributed bundles
|>||We also will need to setup automated tests for the bundles which are graduated. (See https://bugs.eclipse.org/bugs/show_bug.cgi?id=206333)|
Thomas Watson---10/15/2007 09:28:05 AM---The bundles contributed by Prosyst have been in the incubator since July. The codebase Prosyst donated is already production qu
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 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.
equinox-dev mailing list