[cdt-dev] Scheduling update: CDT 2.1 and CDT 3.0

[Douglas Schaefer <dschaefe@xxxxxxxxxx>]

Hey gang, to make sure everyone is kept up to date,

At yesterday's conference call we discussed the delivery schedule for 2.1 
and 3.0. I think it will be easier to schedule in the code freeze date, 
i.e. the date when we can make our first release candidate. Here are the 
proposed code freeze (RC0) dates for the next two releases.

        2.1 - Tuesday, Nov 2, 2004
        3.0 - Tuesday, Apr 12, 2004 (Note this is over a week after 
Eclipse 3.1 has scheduled their code freeze)

After these dates, we'll go into a release candidate cycle until we have a 
build that has satisfactory quality. This usually takes around 4 weeks but 
that depends on how much test pressure we can get from the community 
during this time. If we don't get testing done and bugs found we'll have 
to assume the quality is good enough. (So please help! :-)

As for milestone builds, we should target building CDT 3.0 against the 
milestone releases of Eclipse 3.1 (i.e. not integration builds). We'll aim 
for building on the Tuesday after the Friday milestone releases starting 
with M3 on Nov 9. If we find these CDT milestone builds too unstable, we 
can delay as necessary.

After these releases, we have usually found the need to do a maintenance 
release within a couple of months of the main release and will then 
continue to do maintenance releases as we find major bugs.

Thoughts?

Doug Schaefer, IBM's Eclipse CDT Architect
Ottawa (Palladium), Ontario, Canada