[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gnash-dev] Re: [Gnash-commit] Re: Bugs severity

From: Rob Savoye
Subject: [Gnash-dev] Re: [Gnash-commit] Re: Bugs severity
Date: Thu, 31 Mar 2011 18:19:53 -0600
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20110307 Fedora/3.1.9-0.38.b3pre.fc13 Lightning/1.0b2 Thunderbird/3.1.9

On 03/31/11 17:51, Bastiaan Jacques wrote:

> I think the rest of us were doing it the way Sandro was describing. In
> my case that was more of a knee-jerk response rather than any formal
> agreement to do it that way. I'm actually rather neutral on which way is
> better (it doesn't matter so long as everybody understands "Major" and
> "Blocker" to mean the same things), but obviously different people doing
> different things is going to lead to problems.

  How we define bug severity has never been a decided thing that was
ever discussed. When it was finally discussed, there was a difference of
opinion on the definitions, which obviously is still a problem. Even if
I wrote up definitions on the wiki, I doubt some people would feel like
changing how they classify bug severity. If a consensus decision can't
be made on this, then what happens ? Deadlock ? Endless flame wars over
bug reclassification ? Or a firm decision gets made, and we get back to
doing productive work on Gnash ?

  Personally, as the person that has done most all Gnash releases,
leaving critical bugs unfixed for a release would be bad policy. Also as
the person whose name is on the tarball and the announcement, don't you
think I care about the quality of the release ? Bug reports are one of
the ways to judge what that quality is. I deeply care about the quality
of Gnash. The easy solution would be to stop fighting over stupid stuff
like this, and allow the release manager person (who unfortunately is
me) to define and decide bug severity. There are way more important
things to work on than wasting time arguing over this topic.

  What's really important in a bug report is the debugging, patching,
and fixing comments. The category is minimally useful other than knowing
if it's in a release or master.

        - rob -

reply via email to

[Prev in Thread] Current Thread [Next in Thread]