Re: [cdt-dev] Agenda for Monthly Call

[Brent Nicolle <bnicolle@xxxxxxxxxx>]

Hi Derrick,

Further to our offline discussion, please
add the following two agenda items:

1. The need for a collaborated 3.0 Master
Test Plan, for Component Requirements and for Component Test Plans [Brent]
Collaboration of interested parties
in the testing community will be off-line.

2. Milestone promises and quality exit
criteria [Brent]
Here's something for us all to think
about...

The current draft of the 3.0 Test Plan
(http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/cdt-home/plans/CDT_R3_0_plan.html?cvsroot=Tools_Project)
lists the monthly CDT milestone schedule
(good), and lists a few committed items.  I expect the list of committed
items to grow.
The milestone schedule becomes more
meaningful when promises are made for each milestone.  I expect these
promises can come from various sources and have cascading effects.  For
example:
M2: Project Plan ready
M2 + 2 weeks: Master Test Plan ready.
 Component Requirements docs ready eg. AST/DOM Requirements.  
M3: Component Test Plans ready, eg Performance
& Scalability (P&S) Test Plan, AST/DOM Test Plan.
Each of the components make their own
promises:
M3: P&S benchmark #1 produced (as
promised in Test Plan). AST/DOM test scaffolding ready.
M4: P&S benchmark #2 produced, alert
if degrades from #1.  AST/DOM clients 1 & 2 ready for testing.
M5: P&S benchmark #3 produced, alert
if degrades from #2.  AST/DOM clients 3 & 4 ready for testing.
M6: P&S benchmark #4 produced, alert
if degrades from #3.  AST/DOM formal testing complete.  All UI
frozen. Tech preview; feedback solicited.
RC0: AST/DOM test scaffolding removed.
 All help pages more-or-less complete.  Check-ins for defect
fixes only.
RCn:  P&S is significantly
better than benchmark #1.

In terms of milestone quality exit criteria,
I'd like to see: 
M[3-6]: Build is stable and tested rigorously
for a couple of days, during which destabilizing checkins are held off.
 A list of new feature functionality is announced.
To that end, I'd like to see Milestone
builds produced on the first Monday (not Friday) of the month, and the
official announcement of the tested Milestone availability presumably by
Wednesday. A milestone build which doesn't meet its quality objectives
may be accepted anyhow, deferred, extended, or branched, on a case-by-case
basis as determined by the major stakeholders.

Cheers,

Brent

Brent Nicolle     Email: bnicolle@xxxxxxxxxx
    Tel: (613) 591-7982
Software Quality Developer: Eclipse CDT, Rational Software Architect
IBM Rational Software, 770 Palladium Drive, Kanata, Ontario, Canada.

Derrick Keefe <dkeefe@xxxxxxx>
Sent by: cdt-dev-admin@xxxxxxxxxxx

01/31/2005 10:16 PM

Please respond to
cdt-dev

To	cdt-dev@xxxxxxxxxxx
cc
Subject	[cdt-dev] Agenda for Monthly Call

It's that time already.
 
This is a call for agenda items for this
Wednesday call.  Please respond to this thread.
 
TX 
Derrick