Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:116286
MIME-Version: 1.0
References: <CAOwTYAtOti3+Tv9Cu5fK6bQ3tjAibRHUWOctnQFfGJyaoQYExw@mail.gmail.com>
 <CAF+90c_rrykaHU-U7sBW9cxTPGCk0MzcKkZU-BiH2MiqyNsMQQ@mail.gmail.com>
In-Reply-To: <CAF+90c_rrykaHU-U7sBW9cxTPGCk0MzcKkZU-BiH2MiqyNsMQQ@mail.gmail.com>
Date: Thu, 21 Oct 2021 21:42:15 +0100
Message-ID: <CAEKnhAHTWv-DEWV5vEnkaC9dzjA1oK4m4tOBLb7O2+1X8PC6tg@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: Joe Watkins <krakjoe@php.net>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000af055e05cee2ee14"
Subject: Re: [PHP-DEV] Bugsnet
From: bukka@php.net (Jakub Zelenka)

--000000000000af055e05cee2ee14
Content-Type: text/plain; charset="UTF-8"

On Thu, Oct 21, 2021 at 4:07 PM Nikita Popov <nikita.ppv@gmail.com> wrote:

>
> I'm proposing the following label structure (the list at
> https://github.com/nikic/test-repo/labels is incomplete though): Each
> report has either a bug or feature label. Additionally it starts out with
> the T-needs-triage label. Once a project member triages the report, the
> label is removed and a category label is added instead, e.g. C-OpenSSL for
> issues relating to the OpenSSL extension.
>
> I also have a few more triage labels (T-needs-feedback, T-verified,
> T-invalid, T-wontfix, T-duplicate), but I'm not sure we actually need any
> but the first one or the first two -- I personally don't see a lot of value
> in having a label for why exactly an issue has been closed, the fact that
> it is closed is usually sufficient.
>
>
Have you considered custom fields that are now in beta with some other
features in https://github.com/features/issues ? That seems a bit nicer to
me...

Regards

Jakub

--000000000000af055e05cee2ee14--