Difference between revisions of "COSMOS BUILD SCHEDULE"

Revision as of 13:55, 4 February 2008

	Monday	Tuesday	Wednesday
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			Each subproject lead (or delegate) 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		Finish reviewing all patches from bugzilla. Check in the patch if it passes review. 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	Non-committers attach all patches in bugzilla	Build starts	QA picks up the weekly integration build

@@ Line 15: / Line 15: @@
 |  ||
 ||
-* 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.)
+* Each subproject lead (or delegate) 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.)
 || ||
 |-
@@ Line 30: / Line 30: @@
 ! 4:00 PM
 |
-* Attach all patches in bugzilla
+* Non-committers attach all patches in bugzilla
 ||
 * <font size="5" style="bold">Build starts</font>