Difference between revisions of "WTP Smoke Test Results R324 05112011"
(→Release Approval votes)
|Line 49:||Line 49:|
| align="center" | [[Image:
| align="center" | [[Image:.gif]]
Latest revision as of 13:00, 19 May 2011
Release Approval votes
Mechanically, this page is just like our typical "smoke test" page ... so I've left the instructions below the same as always ... but, what we are asking for here is final documenation that we are ready to release WTP 3.2.4. It is not a time for "new bug testing", but a good time to verify and confirm our final build is as you expect it to be.
Committers and Project Leads, please complete by Friday, 5/13, noon Eastern (at the latest, or let us know if that is not possible).
We will officially "release" this build on 5/20, assuming no blocking problems are found during our "quiet week".
Use a red X (fail) icon () to signify that the build should not be promoted, that a respin is required. In that case, please provide bug number and be sure those that need to fix something are aware of it, and can arrange for a respin. Once the issue has been fixed, and confirmed, change the red X to a green check mark with the build Id where is was verified, so those doing the promotion know its ready to go.
If a smoke test does not pass but the build can still be promoted, use a green check mark (ok) icon () but then document in the comments bug numbers, how the smoke test fails, workarounds, or cautions about the build.
If a build can be promoted and no issues were found, simple use the green check mark and include the initials or names of who performed the test.
Remember the significant column for promoting a build is the left-most project column. If some component within a project has not (or can not) be tested, the Project Lead should either make sure someone does the test, or make a judgment call on if the build (from their project's point of view) can be promoted or not. If the smoke test could not be performed, a note should be made in the comments section that it wasn't performed, why, and why that should prevent promotion.
Keep in mind the threshold for promoting a build gets higher as we near a milestone or near a release.
|Java EE||DG - 345709 IGD - 345765|
|Web Services, WSDL||Web Services (mh)|
|Source Editing||XML + JSP (ns)|
|Release Engineering|| (dw) releng test failure does not effect the delivered build See bug 345461. |
There are also oddities that will occur with updating from Java EE IDE package, but nothing blocking. See bug 345503.