I would say just smoke test the most recent one. I haven't looked at this one, nor do I understand why we are getting so many JUnit failures (nor why they haven't been "cleaned up" yet), but, as a general rule, the most recent one if the right one to test, and you can simply document which one you tested.
Though not all teams have said so, I'm 99.9% sure any problems are with the tests ... and not the build itself. Thanks, From: "Raev, Kaloyan" <[EMAIL PROTECTED]> To: "General discussion of project-wide or architectural issues." <[email protected]> Date: 01/21/2008 12:26 PM Subject: RE: [wtp-dev] 3.0 M5 I build declaration delayed Hello, What happens now with the smoke testing? Do we smoke test I20080118133216 as requested in wtp-releng, or we are still waiting for a build with 0 JUnit failures? Greetings, Kaloyan From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Helen Zhang Sent: Friday, January 18, 2008 11:20 PM To: [email protected] Subject: [wtp-dev] 3.0 M5 I build declaration delayed 3.0 M5 I build declaration has been delayed due to failing Junit tests that delayed this weeks smoketest. We are expecting to declare a clean build on Monday. We ask that committers to please do NOT release any changes till after we have a clean I build declared on Monday. Thank you! Regards, Helen Zhang Release Engineer, Project Manager Rational Architecture Management Project Management Office Eclipse Webtools Platform (WTP) IBM Toronto Software Lab | 8200 Warden Ave. | Markham | L6G 1C7 Email: [EMAIL PROTECTED] | Phone: 905-413-3443 | T/L: 969-3443 _______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
smime.p7s
Description: Binary data
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
