diff options
| author | Jonathan Biemond <jonbiemond@gmail.com> | 2026-04-05 18:40:05 +0200 |
|---|---|---|
| committer | Natalia <124304+nessita@users.noreply.github.com> | 2026-04-17 17:28:06 -0300 |
| commit | 29e31fbe87d56d0b2ee824c77113e56ed4a44f64 (patch) | |
| tree | 66aa428f06d95d9cfb6ab4d3cf895e1db55db2e5 | |
| parent | 69d86004f7b3c9ed223c18998c2b799d1670474f (diff) | |
[6.0.x] Clarified that reporters shouldn't set their own tickets as "Accepted".
Backport of d687d412a9abd9c80e31945f16ce32c020512394 from main.
| -rw-r--r-- | docs/internals/contributing/triaging-tickets.txt | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/internals/contributing/triaging-tickets.txt b/docs/internals/contributing/triaging-tickets.txt index 6643341ee7..756db02b08 100644 --- a/docs/internals/contributing/triaging-tickets.txt +++ b/docs/internals/contributing/triaging-tickets.txt @@ -415,6 +415,10 @@ Then, you can help out by: However, we do ask the following of all general community members working in the ticket database: +* Please **don't** promote your own tickets to "Accepted". Another community + member should review the report and set this stage after reproducing and + confirming the issue. + * Please **don't** promote your own tickets to "Ready for checkin". You may mark other people's tickets that you've reviewed as "Ready for checkin", but you should get at minimum one other community member to |
