[cdt-dev] Fw: [eclipse-dev] 3.0 M5 build schedule

[Douglas Schaefer <dschaefe@xxxxxxxxxx>]

In case you aren't following eclipse-dev, here is the E3.0M5 build 
schedule.

Doug Schaefer, Senior Software Developer
IBM Rational Software, Ottawa, Ontario, Canada
----- Forwarded by Douglas Schaefer/Ottawa/IBM on 11/17/2003 01:24 PM 
-----

Kim Moir/Ottawa/IBM@IBMCA 
Sent by: eclipse-dev-admin@xxxxxxxxxxx
11/12/2003 02:18 PM
Please respond to
eclipse-dev


To
eclipse-dev@xxxxxxxxxxx
cc

Subject
[eclipse-dev] 3.0 M5 build schedule







Eclipse 3.0 Milestone 5 build (3.0 M5) is planned for Friday, November 21. 
 

The updated build schedule is available here... 

http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-releng-home/buildSchedule.html 


In brief, the 3.0 M5 build schedule is as follows.... 

Tuesday Nov 18, 08:00 EST - 3.0 M5 Warm-up build 
-this is just a warm up 
-rebuilds will only be run if their are compile errors or missing plugins. 
 (Same as the integration build rebuild policy) 

- Wednesday, Nov 19, 00:10 (in lieu of nightly build) EST 
  - 3.0 M5 Test candidate build 
  - this is the real M5 build 
  - goal: a good build for the test pass on Thursday 
  - all teams need to sign off on  that candidate build is good enough to 
use for Thursday's test pass 
  - rebuild at 8 am without  waiting for status from all teams if a 
rebuild is requested 
  - rebuild at noon without waiting for status from all teams if a rebuild 
is requested 
  - additional rebuilds as necessary when all teams contributing to 
rebuild are ready 
  - for a rebuild, only team(s) requesting the rebuild need to recheck and 
sign off (although they may request other teams to revalidate potentially 
affected functionality) 

- Thursday, November 20 (all day) - 3.0 M5 Test pass 
  - intensive 1-day test pass on M5 candidate 
  - identify any critical problems and supply critical fixes by 16:00 EST 

- Thursday, November 20, 16:00 EST - 3.0 M5 Release candidate 
  - this is the final M5 build 
  - goal: a good build to release as 3.0 M5 on Friday 

- Friday, November 21 
  - all teams need to sign off that the release candidate is good enough 
to declare as 3.0 M5 
  - rebuild at noon without waiting for status from all teams if a rebuild 
is requested 
  - additional rebuilds as necessary when all teams contributing to 
rebuild are ready 
  - for a rebuild, only team(s) requesting the rebuild need to recheck and 
sign off (although they may request other teams to revalidate potentially 
affected functionality) 
  - declare 3.0 M5 available