[Top][All Lists]

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

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

From: Sandro Santilli
Subject: Re: [Gnash-dev] Re: [Gnash-commit] Re: Bugs severity
Date: Sat, 2 Apr 2011 16:54:50 +0200

On Fri, Apr 01, 2011 at 01:25:06PM -0400, Diptorup Deb wrote:

> The bug severity does not really matter in between releases (unless it is
> something which needs an immediate patch e.g. security). And it can be left
> to the individual developer looking into the bug. Rob I believe this should
> be fine since you as the maintainer cum release manager still do not want to
> expend time in micro managing the severity level of each bug. Best left to
> each developer's style and understanding, something which allows him/her to
> prioritise on their own.
> Before each release based on the tracker reporting, the team consensually
> decide which all bugs are release 'Blockers'. Based on -
> How much time it may need for analysis and fixing.
> What is the complexity? (Sandro I have no inputs on this one mate :-) You
> guys are the gurus so leave it best to your judgement)
> How big is the impact of the bug vis-a-vis overall Gnash usage.
> When the release needs to go out realistically.
> After this if some bugs designated as a Blocker are not fixable within the
> above constraints, let the release manager have a final say (in consultation
> with the person assigned to the bug) on what needs to be done. Whether delay
> the release or downgrade the bug.
> If the team can address these with honesty and is a little more
> accommodation for each other, think this may work.

The above is fine to me.


  ()   Free GIS & Flash consultant/developer

reply via email to

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