| RE: [cdt-dev] M7 confusion |
|
The plan has been updated. I also
encourage everyone to take a look at it and make sure it represents what we’re
actually doing. (e.g. I just marked the Windows SDK feature deferred). A number
of people have asked about the plan and I’d like to refer them here as a
summary of what we’re delivering. Thanks,
From: cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-bounces@xxxxxxxxxxx] On
Behalf Of Absolutely, thanks Mikhail and I apologize
to everyone for not fixing that. I knew there was something I was
forgetting… I’ll fix it ASAP.
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Sennikovsky, Mikhail Thanks, Doug, Basically the source of confusion with
milestones for me was the http://wiki.eclipse.org/index.php/CDT/planning/4.0Plan
page that says:
The code
freeze date is the RC0 date which marks the beginning of the ramp down. All
features should be implemented and only bug fixes of increasing criticality
should be fixed marching towards the Europa release date of Friday, June 29,
2007. Probably we should fix this on that page? Thanks, Mikhail From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of I see people are still confused about M7. I don’t
blame them. It’s odd that a milestone happens after our RC0. But to
reiterate, RC0 is April 27 ß Feature complete,
bug fixing only after this date RC1 is May 11 ß This is also known
as M7 to satisfy our Europa delivery for Europa M7 Again the idea is that there is so much feature content
going into 4.0, we need a full two months of rampdown to make sure the release
at the end of June is of good quality. The Europa M7 is too late to meet our
needs. Please feel free to ask any question to make sure this is
clear, Cheers,
|