trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: March 2012

Re: [trinity-devel] [SOLVED] Re: [trinity-devel] tdebase cmake Failure: CMake Error at konqueror/sidebar/cmake_install.cmake:56

From: "Timothy Pearson" <kb9vqf@...>
Date: Sun, 4 Mar 2012 17:49:22 -0600
>> > I propose a team goal that R14 is not released with any
>> unresolved Blocker, Critical, or Major bug reports. Possibly
>> even add 40 to 50% of the Normal reports too. Is this
>> doable? Agreeable?
>> >
>>
>> +1 - we will sell no wine until it's time....
>>
>> There is a huge unrecognized benefit in taking a few
>> extra weeks to clean everything up before a release compared to the
>> time/manpower
>> required after release to correct bugs easily squashed before release.
>> R14
>> should be as clean as we can make it :)
>
> Curious, I ran some queries in the bugzilla. Here are the number of
> unresolved open bug reports in the aforementioned categories:
>
> Blocker: 22 (11 with patches)
> Critical: 24 (2 with patches)
> Major: 67 (4 with patches)
> Normal: 144 (9 with patches)
>
> Total of the above: 257
>
> Total bug reports related to building/compiling: 36
>
> Total open unresolved bug reports, all levels, not tagged as wishes or
> enhancement reports: 346
>
> How many of these bug reports remain current and valid remains to be seen.
>
> Enhancement/wish list requests: 116
>
> Proposed R14 release date per wiki: Spring 2012. June 19 is the last day
> of spring, which means 104 days. To resolve all Blocker, Critical, Major
> and 50% of Normal bug reports means 185 bug reports resolved. That means
> 1.8 bug reports per day. To resolve all Normal bugs in the same period
> means 2.5 bug reports per day. To resolve all unclosed bug reports means
> 3.3 bug reports per day. Assuming no new bug reports being filed.
>
> Darrell

Yep, not doable by any means.  Blocker reports will be fixed for R14.0,
not sure about the rest...

Tim