RE: [cdt-dev] CDT 3.0 Milestones

[Derrick Keefe <dkeefe@xxxxxxx>]

-----Original Message-----
From: cdt-dev-admin@xxxxxxxxxxx [mailto:cdt-dev-admin@xxxxxxxxxxx] On Behalf
Of Douglas Schaefer
Sent: Monday, February 07, 2005 12:09 AM
To: cdt-dev@xxxxxxxxxxx
Subject: Re: [cdt-dev] CDT 3.0 Milestones

I thought we had suggested keeping the Friday milestone date. This is the 
date the milestone is declared. I really don't anticipate much happening 
on the weekend. A Friday declaration would probably be more practical and 
allow us to gain an extra weekend of user testing (who won't take it until 
the milestone is declared).
[Derrick Keefe] 
[Derrick Keefe] This date will represent the date that developers need to
have there features checked in. Setting a date for a "stable" build is less
definite as it will depend on the results of our testing and the ability to
turn around fixes. So it could be Wednesday, Thursday, Friday etc.  The
important thing will be for us to declare a milestone build stable when it
is.

I would also suggest using the same numbers as Eclipse so that people know 
which milestone we're lining up with. So that would put CDT 3.0 M5 on 
March 11. We could use the Tuesday build on March 8 as the candidate with 
rebuilds as necessary to meet our desired quality criteria by the Friday. 
We can also consider going kamikaze and trying M5 the week before 
EclipseCon.
[Derrick Keefe] 
[Derrick Keefe] If people agree that this would be helpful, I'd be happy to
change this.  BTW when we need to set milestones that do not line-up to
theirs, we could define milestones such as 5.2.

I'm not sure we need a milestone build before that. I don't think there's 
been enough significant user-visible content at this stage to warrant it. 
Eclipse 3.1 M4 is pretty early and it's quality shows so I'm not sure 
there's much demand for a CDT build that runs against it. If people are 
desperate, they can take a weekly build.
[Derrick Keefe] 
[Derrick Keefe] I agree, so that's -2 for a February Build.

I'd be happy to debate this issue more, though.

Doug Schaefer
Ottawa Lab, IBM Rational Software Division



Derrick Keefe <dkeefe@xxxxxxx> 
Sent by: cdt-dev-admin@xxxxxxxxxxx
02/06/2005 10:28 PM
Please respond to
cdt-dev


To
"'cdt-dev@xxxxxxxxxxx'" <cdt-dev@xxxxxxxxxxx>
cc

Subject
[cdt-dev] CDT 3.0 Milestones







Based on last weeks call, here are the purposed CDT 3.0 Milestone Dates in
relation to Eclipse 3.1.  I'm not sure how useful a milestone build is 
this
month (M1) please comment.


Eclipse 3.1 M4 based builds 

CDT 3.0 M1 Monday, Feb. ? ,2005 - stable build reflecting progress. 

Eclipse 3.1 M5 Feb 18,2005 

CDT 3.0 M2 Monday, Mar.14 ,2005 - stable build reflecting progress 

Eclipse 3.1 M6 Apr 1, 2005 API complete - API freeze

CDT 3.0 M3 Monday, April 11, 2005 - API freeze, stable build focus on
clearing bug backlog.

Eclipse 3.1 M7 May 13, stable build - feature complete - development 
freeze
- lock down and testing begins

CDT 3.0 M4 Monday, May 30, 2005 - stable build, feature complete, RC0 
Lock down and external testing begins with M4 and progresses through a
series of test-fix phases against candidate releases. 

Release candidate builds are planned as follows (M4 is RC0)
                 Note these dates are conditional on Eclipse 3.1 schedule 
CDT 3.0 RC1 Monday,  June 13,2005 - Release Candidate 

CDT 3.0 RC2 Monday, June 27, 2005 - Release Candidate 

Eclipse 3.1 GA expected ~July 1 

CDT 3.0 RC3 Monday, Jul. 18, 2005 - Release Candidate
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev


_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev