From 39ea109008e7de1233f7b650fd88980f037b5c1b Mon Sep 17 00:00:00 2001 From: Dmitry Khalanskiy <52952525+dkhalanskyjb@users.noreply.github.com> Date: Wed, 20 Dec 2023 14:14:09 +0300 Subject: [PATCH] Specify the rules for release candidate feedback (#3990) --- .github/ISSUE_TEMPLATE/rc_feedback.md | 28 +++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/rc_feedback.md diff --git a/.github/ISSUE_TEMPLATE/rc_feedback.md b/.github/ISSUE_TEMPLATE/rc_feedback.md new file mode 100644 index 0000000000..02f06dda9e --- /dev/null +++ b/.github/ISSUE_TEMPLATE/rc_feedback.md @@ -0,0 +1,28 @@ +--- +name: Release Candidate release feedback +about: Something used to work, but broke in an RC release? +title: 'RC:' +labels: bug +assignees: '' + +--- + + + +**What broke?** + +Even a vague description suffices. If you want to search for a reproducer or +narrow the issue down, this would help a lot, but the most important thing is +letting us know that there is a problem at all as soon as possible. Otherwise, +we'll just publish a stable release with this problem while you're looking for a +reproducer! + +**Did I check that setting the version to the latest stable release fixes the problem?** + +Yes.