Definition of a "blocker" bug ?

[Jeremy Allison]

On Tue, Jan 05, 2010 at 09:30:06PM -0500, Scott Lovenberg wrote:
> Jeremy Allison wrote:
>> Volker and I ended up having an interesting
>> discussion in a bug report about the meaning
>> of the term "blocker" as a severity catagory
>> in bug reports.
>>
>> I have a definition I'd like to propose -
>>
>> A "blocker" bug that will prevent a release
>> is one of the following problems:
>>
>> Security holes.
>> Data corruption.
>> Resource leaks (covers fd's, memory etc.)
>> Unrecoverable client-visible errors.
>>
>> Let me know what you think.
>>
>> Jeremy.
>>   
> As an user, I'm willing to suffer slight resource leaks if the upshot is  
> faster iteration between releases. Wearing my developer hat, I understand 
> why it would be a blocker, though. Just my $0.02.

The trouble is "slight" resource leaks are very rare. Most
resource leaks can be client triggered, which makes them
not "slight". Maybe I should qualify that to be "client
initiated resource leaks" as a blocker.

Jeremy.