| Summary: | declare 4.2M3 | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Kim Moir <kim.moir> |
| Component: | Releng | Assignee: | Kim Moir <kim.moir> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | cgold, daniel_megert, gheorghe, john.arthorne, Michael_Rennie, Olivier_Thomann, pwebster, remy.suen, Silenio_Quarti, srikanth_sankaran, Szymon.Brandys, tjwatson |
| Version: | 4.2 | ||
| Target Milestone: | 4.2 M3 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Kim Moir
Any comments on the 19 errors in 'e4.ui.test'? We need a 4.2 rebuild for bug 362297. Sorry for the breakage on my part. (In reply to comment #1) > Any comments on the 19 errors in 'e4.ui.test'? Our errors seem to be the incarnation of bug 317126 This is a linux-only testing build. It should not effect the quality of the build. PW 4.2 build I20111028-1100 is running to pick up the e4 source bundles. PW > Platform: > -Text > -Search > JDT: > -Text > -UI Go! Go from User Assistance Go for Equinox. Go from Platform Workspace. Go from: Ant JDT / Platform Debug API Tools PDE Go from Platform UI. PW Given all the active JDT Core committers are 12 hours ahead, I think we will need to go ahead without them. I checked their maps and they haven't made any contribution in three days so I think they should be fine. In future milestones I think we'll need to start this process on Thursday. (sorry Stephan from JDT core is only 6 hours ahead but that is still quite late) Go from SWT. Note that we have discovered two major issues (Bug 362375 and Bug 362374). Given that these occur in two platforms that are not as frequently downloaded (especially for milestone releases), we decided that it was better to just go ahead with the current build rather than asking for a rebuild. These issues will both be fixed for the next integration build. Go from JDT/Core. (In reply to comment #11) > In future milestones > I think we'll need to start this process on Thursday. I was keeping a watch for this this time, Starting it earlier when possible would be appreciated. (In reply to comment #11) > In future milestones I think we'll need to start this process on Thursday. +1. I think we did that before but now the 4.x build comes after the 3.x build and hence we are one day behind schedule. Thanks. Closing Juno M3 now available. |