RE: [cdt-dev] CDT 3.0 Milestones

[John Camelon <jcamelon@xxxxxxxxxx>]

2 cents provided, change expected ...


On one hand (A) we wish to create a
well tested product w/fully documented APIs for our partners to work with.
 
On the other hand, with CDT 2.1, 2.1.1
& 2.0.3 rearing their heads from time to time, (B) few people have
been able to focus (exclusively) on 3.0 features up to this point. 

While I do not necessarily believe that
an April <freeze> milestone is necessary in order to achieve (A),
I do believe that we need a milestone like this in the schedule, and that
it should be respected. 
However, we also run another risk in
that if CDT 3.0 does not demonstrate a significant improvement in quality
(and even content) to 2.X, we run the risk of alienating some of our early
adopters (and even our customers).  

Leo: would an API freeze sometime in
May suit Intel better?

Cheers,
JohnC
www.eclipse.org/cdt

cdt-dev-admin@xxxxxxxxxxx wrote on 02/07/2005 08:21:43
AM:

> I agree that we don't need a milestone until Eclipse 3.1 M5.  I
agree
> with matching the Eclipse milestone numbers.
> 
> I have some issues with the description of the milestone M3.
> 
> > CDT 3.0 M3 Monday, April 11, 2005 - API freeze, stable build
focus on
> clearing bug backlog.
> 
> Please explain in more detail what "API freeze" means.  I
suggest that
> it means that all expected new and changed APIs are documented in
design
> documents and will not change.  How seriously are we going to
adhere to
> the "freeze"?  What will be the process if an implementer
wants to
> change an API after that date? 
> 
> I hope that you are not suggesting that all APIs are implemented.
 If
> so, there won't be much new functionality in the MBS for CDT 3.0.
> "Stable build focus on clearing bug backlog" also seems
to suggest that
> all functionality is implemented.
> 
> Regards,
> Leo Treggiari
> 
> 
> -----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).
> 
> 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.
> 
> 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.
> 
> 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
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-dev