Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

WTP Smoke Test Results R330 06062011

Indigo Release Promotion 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.3.0. 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. (New bugs are welcome, of course, but we would not respin for anything other than a release-blocking bug).

Committers and Project Leads, please complete by Monday, 6/6, 5 PM Eastern (at the latest, or let us know if that is not possible).

We will officially contribute this build to Indigo RC4 on 6/8, and assume it will be our code to use for final Release on 6/22, unless some blocking problem is found during our "quiet week".

There are no plans to respin with our prereqs final (or RC4) versions but feel free to test with them as they become available. While there is no further formal "signoff" after RC4, the assumption is that committers and adopters will continue to test, in some form, until the official release, so if any release-blocking problems are found, feel free to bring them to our attention at any time.

Instructions:

Use a red X (fail) icon (Fail.gif) 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 (Checkmark.gif) 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.

This Week's Results
Project Vote Initials Comments
Java EE Checkmark.gif SDD
JSF Checkmark.gif IT
Dali Checkmark.gif njh
Server Checkmark.gif EY (passed with minor bug 348613)
Web Services, WSDL Checkmark.gif Checkmark.gifWeb Services (mh)

Checkmark.gifWSDL (mh)

Checkmark.gifJAXWS (sc)

JSDT Checkmark.gif cmj
Source Editing Checkmark.gif Checkmark.gifXML + JSP (ns)

Checkmark.gifXSD (mh)

Release Engineering Questionmark.gif


Smoke Test ok to promote vote = Checkmark.gif
Smoke Test do not promote vote = Fail.gif
Smoke Test Pending = Questionmark.gif


Back to the WTP Smoke Test Results Main Page

Back to the top