Re: [wtp-releng] Ready for vote for WTP 2.0: R-2.0-200706260303 and remi

[Chuck Bridgham <cbridgha@xxxxxxxxxx>]

+1 for J2EE - Thanks  (Sorry for
missing this note)

- Chuck

Rational JEE Tooling Team Lead
IBM Software Lab - Research Triangle Park, NC
Email:  cbridgha@xxxxxxxxxx
Phone: 919-254-1848 (T/L: 444)

David M Williams/Raleigh/IBM@IBMUS
Sent by: wtp-releng-bounces@xxxxxxxxxxx

06/26/2007 05:14 PM

Please respond to
Webtools releng discussion list <wtp-releng@xxxxxxxxxxx>

To	" wtp-releng" <wtp-releng@xxxxxxxxxxx>
cc
Subject	[wtp-releng] Ready for vote for WTP 2.0: R-2.0-200706260303 and        reminders of final items

This is our proposed release. 

http://download.eclipse.org/webtools/committers/drops/R2.0/R-2.0-200706260303/

The only difference from RC4 is that an about.html file was fixed, and
Dali released a change to correct update manager installs. 

There were some other "R-builds" that I deleted, and I reverted
code, since the JavaDoc problem I was trying to fix was 
not so easily fixable after all (for nitty gritty, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=179206).

So, Component Leads, please document your approval/disapproval to release
this version of WTP as our WPT 2.0/Europa Release. 
This should be done by Noon on Wednesday, at the latest, please. 

In case you've forgotten :) the official component leads are

Konstantin Komissarchik 
Tim DeBoer 
Nitin Dahyabhai 
Chris Brealey 
Chuck Bridgham 
Raghunathan Srinivasan 
Neil Hauge 

Naturally, you are representing your whole component team, so feel free
to confer with them! 

Also, anyone can vote affirmative to show their support! But the Component
Leads are primarily responsible 
for standing behind the release, so we'd like to have a public approval
documented here on wtp-releng. 

Also, any committer can "veto" ... with very good reasons, of
course. 

Reminder of remaining items: 

http://www.eclipse.org/webtools/releases/2.0/release-notes.php
Be sure to document any "release notes" where we feel users should
be warned of some particularly bad bug, 
or an issue (such as migration) that they would want to be aware of before
they upgrade. Also, if there's a limitation 
that you feel "nearly all users" of a particular function would
hit, you may want to warn them of that. 

In general, though, these release notes should be short and brief and point
off to other sources of info (e.g. bugzillas) 
or else no one will read them. 

http://wiki.eclipse.org/WTP_Release_Scorecards_20 
Please continue to "fill out" the scorecard, if you haven't already.





_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng