| RE: [rt-pmc] Tracking compliance for the Helios release |
In Eclipse and Equinox builds we run the api tooling each build that generates a report for us. See http://download.eclipse.org/eclipse/downloads/drops/S-3.6RC2-201005201744/apitools/apitoolsverifications/html/index.html
I would not suggest doing anything that elaborate if you have not been doing so already. The main thing we need to know is if you are referencing internals (non API) from other eclipse projects.
Tom
Douglas Clarke ---06/02/2010 01:12:50 PM---Any advice on the API requirement the requested reports?
From: | Douglas Clarke <DOUGLAS.CLARKE@xxxxxxxxxx> |
To: | Runtime Project PMC mailing list <rt-pmc@xxxxxxxxxxx> |
Date: | 06/02/2010 01:12 PM |
Subject: | RE: [rt-pmc] Tracking compliance for the Helios release |
Not really. That field is meant reference the executive summary that you should have provided to the EMO (in your mini-deck) along with your complete release review slides. If you can sum that up in one or two sentences then I suggest you just put that summary in the field on the portal. Otherwise you can create a small html page on your project site to refer to. I don't think we will be able to have a single executive summary for all of RT. Instead I think each project lead under RT should come up with their own summary.
Tom
Markus Alexander Kuppe ---06/02/2010 12:03:57 PM---On 06/02/2010 06:32 PM, Thomas Watson wrote:
From: | Markus Alexander Kuppe <rt-pmc_eclipse.org@xxxxxxxxxxx> |
To: | rt-pmc@xxxxxxxxxxx |
Date: | 06/02/2010 12:03 PM |
Subject: | Re: [rt-pmc] Tracking compliance for the Helios release |
