The schedule below shows the dates we're expected to finish (bits posted to
Galileo). We've been on a Friday build schedule since early on for this
release so people have a chance to test the build and we have time to respin
if any problem is found.
Regards,
Vivian Kong
IBM Eclipse
CDT
IBM Canada Toronto Lab
"Marc
Khouzam" ---06/05/2009 09:11:13 AM---Hi,
From: |
"Marc Khouzam"
<marc.khouzam@xxxxxxxxxxxx> |
To: |
"CDT General developers list."
<cdt-dev@xxxxxxxxxxx> |
Date: |
06/05/2009 09:11 AM |
Subject: |
FW: [cdt-dev] Galileo
Schedule |
Hi,
I'm been basing myself on the
below email for our delivery dates.
But the builds have been happening two or three days before
those dates.
Was the schedule
changed?
Thanks
Marc
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Schaefer, Doug
Sent: January-09-09 9:41
AM
To: CDT General
developers list.
Subject: [cdt-dev] Galileo Schedule
Hey gang,
I just wanted to highlight the dates we are
expected to have bits available for the Galileo train. We need to plan around
these and the Eclipse gang have gone Google Calendar happy and they aren't the
best way to deal with this.
M4 - Dec 17, 2008
M5 - Feb 3,
2009
M6 - March 16, 2009
M7 - May 4, 2009 - Feature Freeze
RC1 -
May 18, 2009
RC2 - May 25, 2009
RC3 - June 1, 2009
RC4 - June 8, 2009 -
Code Freeze
RC5 - June 15, 2009
The GA date is scheduled for June 26. RC4
is intended to be the code freeze build with RC5 as
contingency.
I'd like to
get peoples thoughts on the freeze state for M6. Should it be an API freeze?
UI freeze? Architecture Freeze? Anti-freeze?
Cheers,
Doug._______________________________________________
cdt-dev
mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
