[cdt-dev] June 6 status on the "Closure of CDT M7" items

[David Daoust <ddaoust@xxxxxxxxxx>]

According to the plan, we have just 1 week left for M7.

Here is the latest weekly summary of the status on the M7 closure criteria:
  

  1.  Clean up the defects in bugzilla on 3.0:
            a.  No open enhancement
requests 
<May 13 --  38 enhancement requests remaining >
<May 20 --  31 enhancement requests remaining >
<May 27 -- 30 enhancement requests remaining >

<June 6 --  26 enhancement
requests remaining > 

            b.  No defects assigned
to an inbox owner 
<May 13 -- I have moved all the inbox enhancement request to a target
milestone of --  but there are still 37 defects on inbox owners that
still need to be triaged> 
<May 20 --There are still 35 defects on inbox owners that still need
to be triaged> 
<May 27 --  There now are 36 defects on the inbox owners.  I
would like to move ALL of them to future -- Any comments?>

<June 6 -- I have moved all of
these defects to "future".   If you believe that a defect
has been moved inappropriately, please reassign it to yourself and move
it back>

            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)
<May 13 -- I do not have an estimate of how many have been triaged,
but I have appended a summary of all the open defects against M7>
<May 20 -- Updated summary of all the open defects against M7 is attached>
<May 27 -- Updated summary of all the open defects against 3.0 and
M7 is attached.> 
<June 6 -- Updated summary of
all the open defects against 3.0 and M7 is attached.>

    2.  All the Features in the plan are complete (there
may be defects open but the functionality is complete and useable.)
<May 13 -- The plan needs to be updated to reflect reality. The plan
currently indicates 8 features complete, and 48 features in-progress>
<May 20 -- The plan is unchanged from last week>
<May 27 -- The plan is unchanged from last week>

<June 6 -- The plan needs to be
updated with the email status reports from the dev mailing list  (I
will do this)> 

    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.
<May 13 -- No-progress> 
<May 20 -- I have been running with eclipse M7 this week, and I suggest
that we switch the weekly builds to Eclipse M7>
<May 27 -- Weekly builds are now on M7.   There are a number
of  Junits run as part of the build -- Note that there are a few failures
that should be addressed before M7 
<June 6 -- That there are a 6
JUnit failures that should be addressed before M7>

    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.
<May 13 -- No-progress> 
<May 20 -- I have placed a starting point in cvs 
       http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/cdt-home/downloads/ReleaseNotes/3.0/CDT-3.0-News.html?cvsroot=Tools_Project>
<May 27 -- No progress>

<June 6 --
The milestone plan is equivalent to the What's new list, so we should
use it.> 
      - Dave

Assignee	3.0	3.0 M7	Grand Total
achapiro@xxxxxxx	1		1
alain@xxxxxxx	25	2	27
aniefer@xxxxxxxxxx	5		5
Devin_Steffler@xxxxxxxxxx	1		1
dinglis@xxxxxxx	3	1	4
dschaefe@xxxxxxxxxx	4	5	9
gheorghe@xxxxxxxxxx	3	7	10
jcamelon@xxxxxxxxxx	10		10
leo.treggiari@xxxxxxxxx	9		9
Mikhailk@xxxxxxx	44	9	53
pmasse@xxxxxxxxxx	1		1
twolff@xxxxxxxxxx	1		1
vhirsl@xxxxxxxxxx	3	8	11
ddaoust@xxxxxxxxxx	1		1
Grand Total	111	32	143