Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-dev] Reminders about 1.5.4 stream

could you remind me please if we are allowed to commit "Tentatively Approved" bugs [1] provided we are ready to back out if a "-1" gets cast? I seem to recall this being the case, but the approval process [2] doesn't discuss it.


Cheers - CB.

Chris Brealey
Senior Advisory Technical Manager, Rational Java Web Services, IBM Canada Ltd.
D3-275, D3/ENX/8200/MKM, 8200 Warden Avenue, Markham, Ontario, Canada, L6G 1C7
cbrealey@xxxxxxxxxx, 905.413.6038, tieline:969.6038, fax:905.413.4920

David M Williams <david_williams@xxxxxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx

03/20/2007 10:27 PM

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

[wtp-dev] Reminders about 1.5.4 stream

This week will be our first I-build towards 1.5.4.


So, while not much time left, if anyone has any fixes to get in early, Wednesday is the day to do it.

We PMC members will try an keep an eye on

But, there's already been a couple of issues that have come up repeatedly:

1)  Before marking for PMC review, please be sure you have component lead review and approval

documented (or, their delegate). And, as always, include who's reviewed, who's tested., etc.

2) While we documented that appropriate bugs for 1.5.4 were "stop ship" bugs ... to avoid distractions from 2.0 work,
there have been some requests based on adopters "hot bug requests".  We discussed at PMC meeting and while
we'd like to keep any "new feature" work to a minimum (in a maintenance release), we agreed they could be
evaluated and handled as exceptions to the rule. I have updated the document at

to explicitly request that bugs which are not true stop ship defects to be documented as hotbugs (if in fact,
they are blocking adopters use of WTP for some scenarios, but not necessarily a defect per se).

wtp-dev mailing list

Back to the top