Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[dtp-dev] UPDATE: Countdown to DTP 1.6M6 and bug density

OK, let me try again, using a different image.

Here in New England on highway exit ramps red signs facing the opposite
direction saying "Wrong Way" are common. Apparently the "Do not enter"
signs didn't have as much impact, so they added these more blunt warnings.
Why isn't it good to go the wrong way up an exit-ramp? Well, it greatly
increases the risk that you'll have a collision with someone who is going
the right way....

Let's look at the DTP 1.6M6 bug density levels this week, starting on
Monday:

3.47 --> 3.79 --> 4.15 --> 4.42       (<== Wrong Way!)

There's a sign saying that we in DTP are greatly increasing the risk of
collision with DTP consumers who are going the right way...

Regards,
John Graham
Eclipse Data Tools Platform PMC Chair
Staff Software Engineer, Sybase, Inc.
http://osmusings.blogspot.com/
http://dataplat.blogspot.com/

----- Forwarded by John Graham/SYBASE on 03/13/2008 11:26 AM -----
                                                                           
             John                                                          
             Graham/SYBASE                                                 
                                                                        To 
             03/11/2008 11:11          dtp-dev@xxxxxxxxxxx                 
             AM                                                         cc 
                                                                           
                                                                   Subject 
                                       Countdown to DTP 1.6M6 and bug      
                                       density                             
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           



DTP 1.6M6 is only 14 working days away, and there are far too many bugs
assigned to the "1.6M6" target milestone. For example, yesterday we had 52
and today 53, which translates into a bug density of 3.47 and 3.79.
Essentially this means that we'll have to resolve 4 bugs per day from now
until 3/28 to clear the M6 target milestone list.

We are very, very unlikely to accomplish this because:

* The counts are only for current bugs, and do not include incoming.
Typically in each milestone there are a number of incoming bugs that must
be addressed for that milestone, and which take a substantial amount of
time to resolve, test. and verify.

* We have never been able to sustain a closure rate of more than 2 bugs per
day. Sure, there have been days. or even a couple of days in a row, when
more than 2 bugs per day were closed, but those periods are rare and there
is no reason to believe that such sprints can be sustained over three
weeks.

* EclipseCon is next week, and thus a number of DTP committers will not be
available to resolve bugs during the conference

We must be very careful to avoid two situations that can arise when the bug
density gets to an impossible level:

* We must not resolve a large number of bugs quickly right at the end of
the milestone cycle, since doing so greatly increases the risk of
additional defect injection. Simply put, rush work at the end of an
iteration is rarely done well, while often at the expense of breaking
builds and creating more bugs in the process.

* We should not wait until the last moment to postpone (reassign) a set of
bugs, since adopters depending on DTP might be impacted by such delays. If
we instead start reassigning bugs out of M6 now, then adopters will have a
reasonable period of time to react and perhaps petition us for
reconsideration if a particular bug really is critical.

So, I'd like to ask every DTP committer to look at their 1.6M6 target
milestone list as soon as possible and make the necessary adjustments. From
my perspective a bug density of around 1.5 bugs per day is reasonable.

Regards,
John Graham
Eclipse Data Tools Platform PMC Chair
Staff Software Engineer, Sybase, Inc.
http://osmusings.blogspot.com/
http://dataplat.blogspot.com/



Back to the top