Re: [other] High Resistance mode?

HI Jiri,

- there are 0 P1 bugs  
- P2 bugs must be all fixed or waived
- there are 4700 or less P3 bugs (target is 3350)

You are right we can fix zero P1-P5 .Quality criteria  is ok BUT there are some annoying bug that affect IDE Quality.
Ex : http://www.netbeans.org/issues/show_bug.cgi?id=118784 Error badges feature unusable if  you cannot believe to tha badges
      http://www.netbeans.org/issues/show_bug.cgi?id=118783 Generating code which triggers a hint looks dumb.

     

On 10/17/07, Jiri Kovalsky <Jiri.Kovalsky@...> wrote:

Hello Thomas and Anuradha,

Anuradha G wrote:

> Developers and Managers need solid stable release add they don't mind
> any delays to make it stable.

Of course people like stable products. Unfortunately, the definition of "stable" is problematic. Do you mean that stable means zero P1-P5 bugs? This can also mean that nobody was testing the product i.e. there are many many hidden and unknown bugs. So it is certainly better to agree on certain distribution of open bugs across priorities _in advance_ and test&fix like crazy during stabilization period. That's why we have you! NetCAT team of selected community members to help us with this task. We said that we will release only if:

- there are 0 P1 bugs
- P2 bugs must be all fixed or waived
- there are 4700 or less P3 bugs (target is 3350)

Do you question this goal?

Thomas Börkel wrote:

>> you are right but also don't forget to take into account how many
>> features were added to NetBeans 6.0. For example count number of modules
>> in 5.5 and compare the number with 6.0. Obviously, the more lines of
>> code, the bigger chance to introduce a bug.
>
> Right. And I do not question this nor do I say that this is not
> understandable. It's just a fact. The question is: Will you accept a
> high number of bugs for a release?

Yes, if we meet given quality criteria and CA survey will not discover any showstopper we can release.

-Jirka

--
Anuradha G