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

Difference between revisions of "WTP/Build/WTP Build Rhythm Schedule"

< WTP‎ | Build
(Wednesday)
(Thursday)
Line 16: Line 16:
  
 
== Thursday ==
 
== Thursday ==
 +
 +
*Weekly candidate build produced (roughly 9 am EST, at the LATEST) and [[WTP Smoke Test Results | smoke test wiki page]] created.
 +
:-Teams should not commit <b><i>any</i></b> more changes until the build is declared. Unless, of course, it is to fix a bug that is blocking declaration of the build. Such bugs should be well documented in a bugzilla and announced to wtp-releng as a "respin request" (even though, the build will run automatically).
  
 
*Team's smoke test and report status on [[WTP Smoke Test Results |wiki page]] by 2 PM EST.
 
*Team's smoke test and report status on [[WTP Smoke Test Results |wiki page]] by 2 PM EST.
 
*If a team needs to respin for a severe issue, the team may do so provided they report a failed smoke test status on [[WTP Smoke Test Results | the wiki]] and send a note to wtp-releng@eclipse.org with the defect number and explanation of which teams will need to re-smoke test the new build.
 
*If a team needs to respin for a severe issue, the team may do so provided they report a failed smoke test status on [[WTP Smoke Test Results | the wiki]] and send a note to wtp-releng@eclipse.org with the defect number and explanation of which teams will need to re-smoke test the new build.
 
*Discuss declaration of the weekly build during the WTP Status Call 2 PM EST.
 
*Discuss declaration of the weekly build during the WTP Status Call 2 PM EST.
 +
 +
*In the event a re-build is required, then a new build must be complete by roughly 9 AM EST Friday.
  
 
== Friday ==
 
== Friday ==

Revision as of 11:28, 12 February 2009

Finding That Sweet WTP Build Rhythm

Monday

  • Team development.

Tuesday

  • Team development.
  • Prerequisite dependencies finalized and in the builds. (This is the goal, but note anyone can request a dependency be updated at any time by posting to wtp-releng@eclipse.org.)

Wednesday

  • Team development

Thursday

-Teams should not commit any more changes until the build is declared. Unless, of course, it is to fix a bug that is blocking declaration of the build. Such bugs should be well documented in a bugzilla and announced to wtp-releng as a "respin request" (even though, the build will run automatically).
  • Team's smoke test and report status on wiki page by 2 PM EST.
  • If a team needs to respin for a severe issue, the team may do so provided they report a failed smoke test status on the wiki and send a note to wtp-releng@eclipse.org with the defect number and explanation of which teams will need to re-smoke test the new build.
  • Discuss declaration of the weekly build during the WTP Status Call 2 PM EST.
  • In the event a re-build is required, then a new build must be complete by roughly 9 AM EST Friday.

Friday

  • Team development continues.

Back to the top