Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[wtp-dev] Respun for 3.1.1

I've put that build on the 'downloads' site (not just 'committers').

When I put it there, it turned out the "3.1.1M" label was sorted last, 
instead of first (most recent) when compared to the "3.1M" labels. So ... 
to avoid confusion ... I just made the "3.1M" versions invisible instead 
of reprogramming the sort algorithms on our web page. 

It will be renamed to an "R" build next week. 

The 'all-in-one' build at
will still need to be respun (I hear) but it should have all of our code 
in it. 


Cameron Bateman <CAMERON.BATEMAN@xxxxxxxxxx>
09/18/2009 02:57 PM
Verified: [wtp-dev] Respinning for 3.1.1
Sent by:

I have verified the ModelManagerImpl fix from the provided build and in 
source from CVS on the 3.1.1 branch.  All required cases are now working.

Verification steps:

1) Use preference to force the timeout value to a very low value (500ms) 
and verify that a deadlock exception is eventually triggered (expected 
2) Use preference with a reasonable value (30000ms) and verify that no 
exception occurs (expected behavior).
3) Use -D system property option with a reasonable preference value 
(30000ms) and a very low system property value (500ms) and verify that the 
system property overrides by producing the same expected behavior as (1).



----- Original Message -----
From: raghunathan.srinivasan@xxxxxxxxxx
To: wtp-dev@xxxxxxxxxxx
Sent: Friday, September 18, 2009 10:11:13 AM GMT -08:00 US/Canada Pacific
Subject: RE: [wtp-dev] Respinning for 3.1.1

We will verify the fix and report status ASAP.

-----Original Message-----
From: David M Williams [mailto:david_williams@xxxxxxxxxx] 
Sent: Thursday, September 17, 2009 7:19 PM
To: wtp-dev@xxxxxxxxxxx
Subject: [wtp-dev] Respinning for 3.1.1

Sorry to say we needed a respin for 3.1.1 after all. One of the blocking 
hotbugs we fixed for this release 
( had a small flaw 
that rendered it useless in context and unfortunately 
this error was not discovered until just today. I think there is just time 

to re-spin, instead of producing an immediate patch. 

The unit tests are running now, and will likely be done around midnight 
(Eastern time). Until then, an early version can be found "as it tests" at

After the tests are complete (e.g. after midnight) it can be found at the 
normal 'committers' area. 

After the JSF team verifies the fix is in the build, I'll promote it to 
'downloads' page. At that time, it will still have the 'M' designation, so 

will rename it on 9/25 for release. I do not think there needs to be any 
formal testing of this final build ... but anyone is welcome to sanity 
check it and let us know if any regressions. 

Apologies for any inconvenience or rework this causes. Do let us know if 
this impacts anyone in ways we are not aware of. 


wtp-dev mailing list
wtp-dev mailing list
wtp-dev mailing list

Back to the top