Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "COSMOS BUILD SCHEDULE"

Line 11: Line 11:
 
* Build team to post an email to cosmos-dev to notify development that the JUnits can begin.
 
* Build team to post an email to cosmos-dev to notify development that the JUnits can begin.
 
  || ||
 
  || ||
|-
 
! 12:00 PM
 
|  ||  ||
 
* Development posts the results of the project JUnits to the cosmos-dev mailing list. (Note: this is not the TPTP JUnits due to time constraints. JUnits are to be run on Windows only.)
 
|| ||
 
 
|-
 
|-
 
! 1:00 PM
 
! 1:00 PM
Line 21: Line 16:
 
* Finish reviewing all patches from bugzilla. Check in the patch if it passes review.  
 
* Finish reviewing all patches from bugzilla. Check in the patch if it passes review.  
 
||  
 
||  
* If all JUnit results good, promote the candidate build to the official weekly build on the download page.
+
* Development posts the results of the project JUnits to the cosmos-dev mailing list. (Note: this is not the TPTP JUnits due to time constraints. JUnits are to be run on Windows only.)
* Once the candidate build is promoted, Build team to send a email to cosmos-dev notifying QA to pick up the build at this time.  
+
 
|| ||  
 
|| ||  
 
|-
 
|-
! 3:59 PM
+
! 3:45 PM
 
|  
 
|  
 
* Attach all patches in bugzilla  
 
* Attach all patches in bugzilla  
 
||  
 
||  
 
* Finish checking in all code for the weekly integration build  
 
* Finish checking in all code for the weekly integration build  
||  || ||
+
||  
 +
* If all JUnit results good, promote the candidate build to the official weekly build on the download page.
 +
* Once the candidate build is promoted, Build team to send a email to cosmos-dev notifying QA to pick up the build.
 +
   || ||
 
|-  
 
|-  
 
! 4:00 PM
 
! 4:00 PM
| || <font size="5" style="bold">Build starts</font> || || ||  
+
| ||  
 +
* <font size="5" style="bold">Build starts</font>  
 +
||  
 +
* <font size="5" style="bold">QA picks up the weekly integration build</font>
 +
|| ||  
 
|}
 
|}

Revision as of 12:43, 4 February 2008

COSMOS Build Schedule

Weekly integration builds schedule

Monday Tuesday Wednesday Thursday Friday
9:00 AM
  • Post the candidate weekly integration build on the downloads page.
  • Build team to post an email to cosmos-dev to notify development that the JUnits can begin.
1:00 PM
  • Finish reviewing all patches from bugzilla. Check in the patch if it passes review.
  • Development posts the results of the project JUnits to the cosmos-dev mailing list. (Note: this is not the TPTP JUnits due to time constraints. JUnits are to be run on Windows only.)
3:45 PM
  • Attach all patches in bugzilla
  • Finish checking in all code for the weekly integration build
  • If all JUnit results good, promote the candidate build to the official weekly build on the download page.
  • Once the candidate build is promoted, Build team to send a email to cosmos-dev notifying QA to pick up the build.
4:00 PM
  • Build starts
  • QA picks up the weekly integration build

Back to the top