Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [wtp-dev] Agenda of the WTP Status Telecon, 2006-06-22

…and then answer any questions, address issues people raise there, provide additional education or pointers into WTP, etc.


From: wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx] On Behalf Of Gerry Kessler
Sent: Thursday, June 22, 2006 11:41 AM
To: General discussion of project-wide or architectural issues.
Subject: RE: [wtp-dev] Agenda of the WTP Status Telecon, 2006-06-22


Lawrence - you can sign me up for the monitoring the SlashDot site.  


What are you looking for?   Just an announcement to the list of a WTP related sighting and a link?   For how long?



Gerry Kessler

WTP JSF Tools Team


-----Original Message-----
From: wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx]On Behalf Of Lawrence Mandel
Sent: Thursday, June 22, 2006 9:26 AM
To: General discussion of project-wide or architectural issues.
Subject: Re: [wtp-dev] Agenda of the WTP Status Telecon, 2006-06-22

Note: Section 1.7.1 contains the news site assignment from the WTP 1.0 release. No one is currently on the hook to cover these sites for WTP 1.5 but I will request volunteers on today's status call. Feel free to volunteer via the dev list if you will not be on the status call.

Lawrence Mandel

Software Developer
IBM Rational Software
Phone: 905 - 413 - 3814   Fax: 905 - 413 - 4920

Jeffrey Liu/Toronto/IBM@IBMCA
Sent by: wtp-dev-bounces@xxxxxxxxxxx

06/22/2006 11:35 AM

Please respond to
"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>






[wtp-dev] Agenda of the WTP Status Telecon, 2006-06-22




See WTP Status Telecons [1] for more information.


1. WTP 1.5 Status

6/22 an I-build produced, if needed

      We do need one. 4 bugs fixed. (Der Ping, Chuck, have you released? marked bugs as fixed?)

               I will start a weekly integration build at noon on Thursday (and pick up final JSF changes too) for
               declaration by noon on Friday. Please plan on some smoke tests in-between there, though the changes
               are small for most. I will label this as our RC6 build, and if we happen to need another one next week, we will
               label it RC6b. Be sure to spread your platform coverage, be sure to check things like if source from an SDK target
      can be imported, etc.,

6/23 an I-build declared

      Reminder that head should be kept "clean" ... in the event we need some late night, late breaking bug, we may need to do
      a quick head build, just as extra care to make sure it builds, runs well from a true build, etc. before its approved. (I hope not,
      but, let's not tempt fate).

Last chance to do any final build, only if needed

all final release zips and update site files must be complete by _the morning_ of this date

6/30 Release goes live ... so, what the heck, take the next day off :)

Note pre-reqs:

As you do your final testing and verifications, please note our final set of pre-reqs.
In particular, the "M" part of the base build has thrown off some people ... its further down on their page, and it is not really "maintenance" ...
it just fit in with their scripts in just the right way. (and RC7 was lucky or something ... maybe they had a bet they wouldn't go past RC7 :)

Note final pre-reqs:

These are most likely the final pre-reqs we build with. Most projects are not planning rebuilds, unless a blocker is found.
I think even if they do re-build next week, for docs or "about" files, any changes would likely not effect us.
Unless you tell me otherwise!

I'd prefer not to re-build, just to re-build, just to avoid churn.
Unless you tell me otherwise!

Do body's expecting any fixes from pre-reqs, right?

1.1 WTP 1.5 Targeted Bugs [1] - Jeffrey Liu

We've entered code freeze. We will not fix a bug unless it is stop ship. We still have 2 bugs targeted to the 1.5 release, can owners provide status for them?


1.2 P1 Bugs [1] - Jeffrey Liu

P1 to us mean release defining. Are we fixing them in 1.5 or defering them? Do we have a good reason why we are defering them? Owners, please provide status.


1.3 Blocking and Critical Bugs [1] - Jeffrey Liu

Use 1.5_deferred in the status whiteboard field to defer a bug.


1.4 WTP 1.5 PMC Approved Bugs [1] - Jeffrey Liu


1.5 WTP 1.5 Hot Bugs[1] and Hot Bug Requests [2] - Jeffrey Liu



1.6 Bugs to be Verified and Closed

We are down to 2023 bugs to be verified and 508 bugs to be closed.



1.7 WTP 1.5 Wrap-up and Post Release

1. New Site Coverage.

WTP newsgroup
- Nitin, Gorkem
The Server Side (
- Naci
InfoWorld (
- Ragu
eWeek (
- Tim
Java Developer's Journal (
- Arthur - Pieter Humphrey

Dr. Dobb's Journal (
- Lawrence
CNet (
- Tim/Pieter
Planet Eclipse (
- This site is an aggregate and does not need specific coverage
EclipseZone (
- Tim
Eclipse Plugin Central (
- Tim D.
TechForge ( - Pieter Humphrey
Code Zoo ( - Pieter Humphrey

ObjectWeb - Naci

FreshMeat - Arthur

Java Pro (
- Chris Judd
JSurfer (
- Albert Almajano
SlashDot (

DevX Forums (

Java Pro (
JSpin (

2. Test Plans -- important to document and be transparent about the type of testing we do (or, don't as the case may be).

3. What's new and noteworthy.

4. Readme (releases notes).

5. Recognition of  contributors

2. Other Business - Open

Test coverage for all WTP classes/methods[1]


Jeffrey Liu
IBM Rational Software
IBM Toronto Lab.
8200 Warden Ave. Markham, Ontario, L6G 1C7
Internal mail: D3/UMZ/8200/MKM (D3-268)
T/L: 969 3531
Tel: (905) 413 3531
Fax: (905) 413 4920
wtp-dev mailing list

Back to the top