[cdt-dev] CDT 2.0 M8 end of game plan

[Douglas Schaefer <dschaefe@xxxxxxxxxx>]

Hey all,

I've been avidly following the Eclipse milestone process and have warmed 
up to it a little. A such, I have convinced my colleagues here at IBM to 
give it a try for their work in the CDT. I don't expect others to follow, 
but to let you know what we're up to, here's our plan.

We are going to take the Eclipse platform M8 build and the Monday morning 
CDT build and bash the heck out of it. The objective is to ensure the 
features we are working on are stable enough for the CDT user community to 
use and that the CDT is overall stable enough (debug may be the known 
exception). The goal would be to ensure that we can declare the Wednesday 
morning CDT build the CDT 2.0 M8 build. I encourage anyone out there who 
has the time to help us out with testing and bug raising. Hopefully we can 
end up with a pretty good M8 especially given the churn in the Eclipse 
platform M8.

And as an update to those who aren't following the platform-releng-dev 
list, fixes are still piling in for the M8 candidate build which should 
have happened already. In general, their process goes: Tuesday - test 
candidate, Wednesday - test and fix, Thursday - milestone candidate, 
Friday - declare milestone. The are about a day behind as the test 
candidate wasn't declared until Wednesday. But they may still pull off a 
Friday milestone yet.

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