From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] [RFC] Add a label `needs-testing` for PRs that have not been tested and unconfirmed issues
Date: Fri, 10 Jun 2022 22:22:54 +0200 [thread overview]
Message-ID: <20220610202254.xL87EhwSPd9HlPdlNw97Rgqw_jGly0bqo15M3lrS7Gc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37448@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]
Closed issue by paper42 on void-packages repository
https://github.com/void-linux/void-packages/issues/37448
Description:
Sometimes people (mostly upstream developers that are not using Void) open a PR they didn't test. I mark them with the `help-wanted` label and add a comment explaining that testing has to be done because just adding the `help-wanted` label would be confusing. I propose adding a new label `testing-needed` for this purpose. This should also be used for PRs that have been tested by the author, but need more testing (openssh, mesa, etc.).
This label would also be added automatically to new bug issues (along with the `bug` label) and removed manually when someone reproduces the bug. Confirmed bugs (without the `testing-needed` label) would be excluded from closing with the stale bot.
https://github.com/void-linux/void-packages/pull/36411#discussion_r850787479
I will give this issue a few days and then create the label if there are no comments.
cc @classabbyamp @0x5c
next prev parent reply other threads:[~2022-06-10 20:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 14:46 [ISSUE] " paper42
2022-06-10 20:22 ` paper42 [this message]
2022-06-10 20:22 ` paper42
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=20220610202254.xL87EhwSPd9HlPdlNw97Rgqw_jGly0bqo15M3lrS7Gc@z \
--to=paper42@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).