There remains some failing JUnits, but it is suspected these are related 
to
and infrastructure changes  external to Eclipse. See bug 171709. 
(These infrastructure changes can effect some end-user functions, but 
it is not in our immediate control). We are looking at how to fix the 
infrastructure issues (since it happens to be with ibm.com) and long 
term looking to make our functionality less fragile to such changes. 

See https://bugs.eclipse.org/bugs/show_bug.cgi?id=171709

But otherwise, 
1.5.3 Fri, 26 Jan 2007 -- 14:24 (UTC)  
should be considered near our release candidate for 
Callisto Winter Maintenance Release (scheduled for 2/16). 
This code stream is now is "lock down" mode and any further 
changes require PMC review and approval. 
The absolutely-no-more-changes-unless-the-machine-catches-fire
date is 2/9, but we encourage 
all adopters to begin their rigorous acceptance testing now to 
be sure no regressions have slipped past us. 

[John will soon provide updates on exact steps of the PMC approval request 
procedure, 
and a web page to summarize status of PMC requests]. 
See 
http://wiki.eclipse.org/index.php/WTP_Release_1.5.x_Maintenance_Plan_and_Policies


I200701261803  Fri, 26 Jan 2007 -- 18:03 (UTC) 
is our weekly declared build toward our M5 milestone, due 2/23, see 
http://wiki.eclipse.org/index.php/Europa_Simultaneous_Release

_______________________________________________
wtp-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Reply via email to