Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Message-Id: <200610051340.k95DeJot024633@d06av02.portsmouth.uk.ibm.com>
In-reply-to: <bc79dd600610050605j54310a78r94560de4b5ef3aa0@mail.gmail.com> 
References: <ddda44ee0610050337l58c78ed9i574d8e34c9c1c3b8@mail.gmail.com>
 <eg2pk4$7vv$1@sea.gmane.org>
 <ddda44ee0610050515v489b377n72d45f0b6729b70c@mail.gmail.com>
 <bc79dd600610050605j54310a78r94560de4b5ef3aa0@mail.gmail.com>
Comments: In-reply-to "Mikhail Fursov" <mike.fursov@gmail.com>
   message dated "Thu, 05 Oct 2006 20:05:32 +0700."
From: Mark Hindess <mark.hindess@googlemail.com>
To: harmony-dev@incubator.apache.org
Subject: Re: [jira] Bugs priorities 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 05 Oct 2006 14:38:46 +0100


On 5 October 2006 at 20:05, "Mikhail Fursov" <mike.fursov@gmail.com> wrote:
> 
> The priority of the bug could be the priority of the scenario this bug
> affects.
> So, we need to select some applications/scenarios and if one of these
> applications failed - the bug is blocker or critical.
> 
> Major as default priority is OK (imo) because it's in the middle of the
> list.

That logic only really works for me if the distribution of bugs by
priority is even.  So for example we'd have as many 'critical' bugs as
'trivial' ones.  I don't think (I hope!) that we do.

Most of our JIRA are classified as major.  Most of the bugs described in
the JIRA issues are actually minor or trivial.

I honestly think the classifications would better reflect reality if we
changed this.

Regards,
 Mark.

> On 10/5/06, Anton Luht <anton.luht@gmail.com> wrote:
> >
> > Hello, Salikh,
> >
> > I just suggest rules to be written explicitly. Every bug submitter
> > tends to think that his bug or his application is the most important -
> > some limits should be put to avoid 90% of bugs being major and
> > critical.
> >
> > On 10/5/06, Salikh Zakirov <Salikh.Zakirov@intel.com> wrote:
> > > Anton Luht wrote:
> > > > Hello,
> > > >
> > > > Maybe it's worth to explicitly specify priorities for various kinds of
> > > > bugs? The advice that appears now near 'priority' drop-down in JIRA
> > > > list is general and not Harmony-specific. Bug submitters make decision
> > > > mostly by his/her intuition.
> > > >
> > > > An example of rule set: VM hangs & crashes - critical, Junit tests
> > > > failures - major, application failures - major, exception
> > > > incompatibility - minor.
> > >
> > > And what guidelines would you recommend for the corner cases,
> > > when something is important for some people, and does not matter for
> > others?
> > >
> > > For example, some people are trying to get Harmony to run x86_64 and
> > ia64 platforms,
> > > while most of the project participants just do not care.
> > >
> > >
> > > ---------------------------------------------------------------------
> > > Terms of use : http://incubator.apache.org/harmony/mailing.html
> > > To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
> > > For additional commands, e-mail: harmony-dev-help@incubator.apache.org
> > >
> > >
> >
> >
> > --
> > Regards,
> > Anton Luht,
> > Intel Middleware Products Division
> >
> > ---------------------------------------------------------------------
> > Terms of use : http://incubator.apache.org/harmony/mailing.html
> > To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: harmony-dev-help@incubator.apache.org
> >
> >
> 
> 
> -- 
> Mikhail Fursov
> 
> ------=_Part_20534_19790021.1160053532326--
> 


---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org