[jbosstools-dev] Re: Fwd: [wtp-dev] API Scannings

[Max Rydahl Andersen]

On Fri, 18 Jan 2008 21:58:14 +0100, Denis Golovin <dgolovin at exadel.com> wrote:

> Alex Kazakov
>
> can do it next week.

cool.

/max

>
> Denis
>
> Max Rydahl Andersen wrote:
>> I always forget this, but we should really get around sending them our adopter report...
>>
>> Anyone up for doing that ?
>>
>> /max
>>
>> ------- Forwarded message -------
>> From: "Raev, Kaloyan" <kaloyan.raev at sap.com>
>> To: "Webtools releng discussion list" <wtp-releng at eclipse.org>, "General discussion of project-wide or architectural issues." <wtp-dev at eclipse.org>
>> Cc:
>> Subject: [wtp-dev] API Scannings
>> Date: Fri, 18 Jan 2008 09:52:17 +0100
>>
>> Hello,
>>
>> I have resurrected the API scanning procedure. Almost all of the API
>> scanning steps run properly. I have still some troubles with the code
>> coverage part.
>>
>> I'd like to catch your attention on the Adopter Breakage Report.
>>
>> I have genereated reports for:
>>  - R2.0.1:
>> http://download.eclipse.org/webtools/downloads/drops/R2.0/R-2.0.1-2007092604
>> 2742/apiresults/api-ref-compatibility.html
>>
>>  - last M2.0.2 I-build:
>> http://download.eclipse.org/webtools/downloads/drops/R2.0/M-2.0.2-2007122206
>> 0852/apiresults/api-ref-compatibility.html
>>
>>  - 3.0 M4:
>> http://download.eclipse.org/webtools/downloads/drops/R3.0/S-3.0M4-2008010509
>> 1323/
>>
>> Compared to the report for R2.0 there are lot of new adopter breakages:
>> http://archive.eclipse.org/webtools/downloads/drops/R2.0/R-2.0-200706260303/
>> apiresults/api-ref-compatibility.html
>>
>> I would like also to request adopters, who have already adopted the WTP
>> 2.0.1 release, to provide updated adopter scanner reports for their product
>> based on WTP 2.0.1. This way we can see the real delta between their last
>> adoption and the current development. How to create the report is described
>> here:
>> http://www.eclipse.org/webtools/adopters/tool.html
>>
>> Greetings,
>> Kaloyan Raev
>> Eclipse WTP Committer
>> <http://www.eclipse.org/webtools/people/person.php?name=raev>
>> Senior Developer
>> NW C JS TOOLS JEE (BG)
>> SAP Labs Bulgaria
>> T +359/2/9157-416
>> mailto:kaloyan.raev at sap.com
>> www.sap.com
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> Hello,
>>
>> I have resurrected the API scanning procedure. Almost all of the API
>> scanning steps run properly. I have still some troubles with the code
>> coverage part.
>>
>> I'd like to catch your attention on the Adopter Breakage Report.
>>
>> I have genereated reports for:
>>   - R2.0.1:
>> _http://download.eclipse.org/webtools/downloads/drops/R2.0/R-2.0.1-20070926042742/apiresults/api-ref-compatibility.html_
>>
>>
>>   - last M2.0.2 I-build:
>> _http://download.eclipse.org/webtools/downloads/drops/R2.0/M-2.0.2-20071222060852/apiresults/api-ref-compatibility.html_
>>
>>
>>   - 3.0 M4:
>> _http://download.eclipse.org/webtools/downloads/drops/R3.0/S-3.0M4-20080105091323/_
>>
>>
>> Compared to the report for R2.0 there are lot of new adopter breakages:
>> _http://archive.eclipse.org/webtools/downloads/drops/R2.0/R-2.0-200706260303/apiresults/api-ref-compatibility.html_
>>
>>
>> I would like also to request adopters, who have already adopted the
>> WTP 2.0.1 release, to provide updated adopter scanner reports for
>> their product based on WTP 2.0.1. This way we can see the real delta
>> between their last adoption and the current development. How to create
>> the report is described here:
>>
>> _http://www.eclipse.org/webtools/adopters/tool.html_
>>
>> Greetings,
>> *Kaloyan Raev*
>> _Eclipse WTP Committer_
>> <http://www.eclipse.org/webtools/people/person.php?name=raev>
>> Senior Developer
>> NW C JS TOOLS JEE (BG)
>> *SAP Labs Bulgaria*
>> T +359/2/9157-416
>> _mailto:kaloyan.raev at sap.com_
>> _www.sap.com_ <file://www.sap.com>
>>
>
> 



-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/