RE: [cdt-dev] Closure process for CDT M7

[Derrick Keefe <dkeefe@xxxxxxx>]

Yes we agreed to change the date by two weeks.

This would change the dates as follows:

CDT 3.0 M7 - Monday, june 13, 2005 - 

Note these dates are conditional on Eclipse 3.1 schedule 
CDT 3.0 RC1 Monday, June 27,2005 - Release Candidate 
CDT 3.0 RC2 Monday, July 11, 2005 - Release Candidate Eclipse 3.1 GA
expected ~July 1 
CDT 3.0 RC3 Wednesday July. 27, 2005 - Final Release Candidate

TO be fair this should be voted on.

Derrick 

> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Treggiari, Leo
> Sent: Tuesday, April 26, 2005 2:40 PM
> To: CDT General developers list.
> Subject: RE: [cdt-dev] Closure process for CDT M7
> 
> Hi Dave,
> 
> > Note that the current plan on the web has M7 scheduled for May 30.
> 
> Yes, but I thought that we agreed at April's meeting to slip that
> date (and all following dates) by two weeks.  Actually, it may not
> have been *exactly* two weeks, it was defined to be the Eclipse M7
> date + n (which "n" I didn't record but was about a 2 week slip).
> 
> > As a starting list, I propose:
> >       1.  Clean up the defects in bugzilla on 3.0:
> >               a.  No open enhancement requests
> >               b.  No defects assigned to an inbox owner
> >               c.  All other defects triaged so that the only open
> >                   defects are ones that we intend to fix before GA.
> >                   (this way anybody who has a defect moved off of 3.0
> >                    can speak up while there is still time to affect
> >                    the contents of 3.0)
> 
> I don't know what an "open" bugzilla is.  I'm guessing that you may mean:
>   Status == (NEW | ASSIGNED | REOPENED) && Target == (3.0* || undefined)
> 
> Thanks,
> Leo
> 
> ________________________________________
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
> Behalf Of David Daoust
> Sent: Tuesday, April 26, 2005 9:23 AM
> To: cdt-dev@xxxxxxxxxxx
> Subject: [cdt-dev] Closure process for CDT M7
> 
> 
> 
> I would like to start some discussion around some guidelines to define the
> exit criteria for M7.  (i.e.  all these conditions must be met before we
> declare M7).    I want to make sure that we agree now, so that there are
> no "bumps in the road" as we approach GA.     Note that the current plan
> on the web has M7 scheduled for May 30.
> 
> As a starting list, I propose:
>        1.  Clean up the defects in bugzilla on 3.0:
>                a.  No open enhancement requests
>                b.  No defects assigned to an inbox owner
>                c.  All other defects triaged so that the only open defects
> are ones that we intend to fix before GA.  (this way anybody who has a
> defect moved off of 3.0 can speak up while there is still time to affect
> the contents of 3.0)
> 
>        2.  All the Features in the plan are complete (there may be defects
> open but the functionality is complete and useable.)
> 
>        3. There has been a sanity run on the M7 build (using Eclipse M7) -
> - we need to define what the extent of this testing is..
> 
>        4.  We have a preliminary "What's new" list for 3.0.  This list
> should cover the entire development of 3.0 so that the community can help
> with the testing/validation.
> 
> Please let me know if you think that the items are good, bad, or just
> ugly.   Also if you have additional items, I would like to add them to my
> list.
> 
> 
>        - Dave
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev