ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: Alexander Bokovoy <a.bokovoy@sam-solutions.net>
To: devel@linux.iplabs.ru
Subject: Re: [devel] severities
Date: Mon, 1 Oct 2001 11:30:32 +0300
Message-ID: <20011001113032.D21601@pc152.belcaf.minsk.by> (raw)
In-Reply-To: <20010930135703.A26549@linux.ru.net>

On Sun, Sep 30, 2001 at 01:57:03PM +0400, Peter Novodvorsky wrote:
> Привет!
> 
> Задался я вопросом, как бы нам классифицировать  наши  баги.
> Вот например как  это делает mantis по  умолчанию:
>     *  block - prevents further work/progress from being made
>     * crash - crashes the application or OS
>     * major - major bug
>     * minor - minor bug
>     * tweak - needs tweaking
>     * text - error in the text
>     * trivial - being nitpicky
>     * feature - requesting new feature
> 
> Вот как это делается в  Debian:
>    critical
>           makes unrelated software on the system (or the whole system)
>           break, or causes serious data loss, or introduces a security
>           hole on systems where you install the package.
>    grave
>           makes the package in question unuseable or mostly so, or causes
>           data loss, or introduces a security hole allowing access to the
>           accounts of users who use the package.
> 
>    important
>           any other bug which makes the package unsuitable for release.
> 
>    normal
>           the default value, for normal bugs.
> 
>    wishlist
>           for any feature request, and also for any bugs that are very
>           difficult to fix due to major design considerations.
> 
>    fixed
>           for bugs that are fixed but should not yet be closed. Bugs
>           fixed by non-maintainer-uploads have their severity set to
>           fixed.
> 
> Я хочу  поменять severities, так как mantis'овские  severities  меня
> не устраивают  из-за пересечений  между  классами багов.  например  класс
Меня модель Дебиана устраивает.
-- 
/ Alexander Bokovoy
$ cat /proc/identity >~/.signature
  `Senior software developer and analyst for SaM-Solutions Ltd.`
---
Beam me up, Scotty!  It ate my phaser!
_______________________________________________
Devel mailing list
Devel@linux.iplabs.ru
http://www.logic.ru/mailman/listinfo/devel


      parent reply	other threads:[~2001-10-01  8:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-30  9:57 Peter Novodvorsky
2001-09-30 11:11 ` Alexey Voinov
2001-10-01  8:30 ` Alexander Bokovoy [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20011001113032.D21601@pc152.belcaf.minsk.by \
    --to=a.bokovoy@sam-solutions.net \
    --cc=devel@linux.iplabs.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

ALT Linux Team development discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
		devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
	public-inbox-index devel

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git