From: "Michał Górny" <mgorny@gentoo.org>
To: <gentoo-dev@lists.gentoo.org>
Cc: <bugzilla@gentoo.org>
Subject: Re: [gentoo-dev] [RFC] bugs.g.o: Killing VERIFIED state, possibly introducing STABILIZED
Date: Fri, 17 Jun 2016 11:02:45 +0200 [thread overview]
Message-ID: <20160617110245.49823b35.mgorny@gentoo.org> (raw)
In-Reply-To: <20160616150213.47f09bc4.mgorny@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]
On Thu, 16 Jun 2016 15:02:13 +0200
Michał Górny <mgorny@gentoo.org> wrote:
> Hello, everyone.
>
> Here's the third bugs.g.o redesign RFC.
>
> This time it's about closed bugs. Right now we have two states for
> them: RESOLVED and VERIFIED.
>
> RESOLVED is the usual state that the developers use when they close
> a bug. It's also the only state that could be directly transferred from
> other states.
>
> VERIFIED is used scarcely, and not really consistently. It can only be
> used on RESOLVED bugs, and sometimes users use it to confirm that
> the bug is resolved.
>
> To be honest, I don't really see the need for VERIFIED state. Since
> it's used scarcely, it can't be really relied upon. Some users use it
> completely incorrectly (e.g. when the bug should be reopened instead).
Since nobody seemed to mind, I've disabled VERIFIED now. I've also
loosened the workflow so that all (old) VERIFIED bugs can be reopened
directly.
For stabilization thing, I'm going to wait for more replies/ideas.
--
Best regards,
Michał Górny
<http://dev.gentoo.org/~mgorny/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 949 bytes --]
next prev parent reply other threads:[~2016-06-17 9:03 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 13:02 [gentoo-dev] [RFC] bugs.g.o: Killing VERIFIED state, possibly introducing STABILIZED Michał Górny
2016-06-16 13:14 ` Kristian Fiskerstrand
2016-06-16 13:19 ` James Le Cuirot
2016-06-16 13:20 ` Kristian Fiskerstrand
2016-06-16 14:00 ` M. J. Everitt
2016-06-17 13:52 ` Michał Górny
2016-06-17 13:58 ` Rich Freeman
2016-06-17 14:00 ` Alexander Berntsen
2016-06-17 14:02 ` Michał Górny
2016-06-17 16:00 ` Kristian Fiskerstrand
2016-06-17 16:41 ` Rich Freeman
2016-06-17 16:46 ` Kristian Fiskerstrand
2016-06-17 17:05 ` Brian Dolbec
2016-06-17 17:26 ` Kristian Fiskerstrand
2016-06-17 17:39 ` Rich Freeman
2016-06-19 22:00 ` Raymond Jennings
2016-06-16 13:18 ` Davide Pesavento
2016-06-16 13:25 ` Andrew Savchenko
2016-06-16 14:51 ` Kent Fredric
2016-06-16 21:57 ` Andreas K. Huettel
2016-06-16 22:05 ` Kristian Fiskerstrand
2016-06-17 7:37 ` Alexander Berntsen
2016-06-17 7:50 ` Michał Górny
2016-06-17 7:55 ` Alexander Berntsen
2016-06-17 7:58 ` Kristian Fiskerstrand
2016-06-17 11:50 ` Rich Freeman
2016-06-17 11:58 ` Kristian Fiskerstrand
2016-06-17 12:18 ` Rich Freeman
2016-06-17 13:02 ` Kristian Fiskerstrand
2016-06-17 13:26 ` Kristian Fiskerstrand
2016-06-17 13:48 ` Rich Freeman
2016-06-17 15:33 ` Kristian Fiskerstrand
2016-06-17 16:43 ` Rich Freeman
2016-06-16 21:58 ` Andreas K. Huettel
2016-06-17 9:02 ` Michał Górny [this message]
2016-06-17 9:12 ` Alexander Berntsen
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=20160617110245.49823b35.mgorny@gentoo.org \
--to=mgorny@gentoo.org \
--cc=bugzilla@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox