Re: Reopen bugs closed with resolution ERRATA?
On Thu, 2016-09-22 at 06:57 +, Joachim Frieben wrote: > Unfortunately, I still ignore the current policy for reopening a > closed bug, in particular those resolved as ERRATA. The documentation > page "BugStatusWorkFlow" should get really amended in this respect. To be totally honest, that page is...you know...kinda theoretical. It was my best attempt (several years ago) to give a kind of very rough 'average' of how all the different teams tracking Fedora bugs actually do stuff. In practice, different maintainers do different things, there's never been a point at which Fedora decided this is The Policy and everyone must follow it exactly, so the page is...a best effort at very approximately explaining how things work in the real world. It would probably be a good idea to revise that page and make this clearer, really, if someone wants to do that it'd be great. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Reopen bugs closed with resolution ERRATA?
Unfortunately, I still ignore the current policy for reopening a closed bug, in particular those resolved as ERRATA. The documentation page "BugStatusWorkFlow" should get really amended in this respect. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Reopen bugs closed with resolution ERRATA?
On Wed, 2016-09-21 at 18:40 +, Joachim Frieben wrote: > The page BugZappers/BugStatusWorkFlow displays the work flow which > applies to a Fedora bug. However, no policy is given about reopening > a closed bug. At the bottom of the page, the reader is referred to "A > Bug's Life Cycle" for further information. Here, we read > > "CLOSEDÂ > This bug fix has been resolved by the Assigned Engineer. The CLOSED > state includes the resolution field which describes why a bug report > is closed. See Resolution descriptions. If the CLOSED resolution > ERRATA is set, the bug report cannot be reopened. Instead, enter a > new bug report for a new problem." > > The expression "cannot be reopened" is ambiguous. Now, some of my > bugs closed with resolution ERRATA have been reopened by other users. > Is this procedure allowed or should indeed a new bug be created > instead which is what I was doing in the past? That text really doesn't apply to Fedora at all. It's a RHEL consideration. We should probably reconsider having the link at all, or at least have stronger wording about the fact that the 'Bug's Life Cycle' page is only very partially applicable to Fedora... -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Reopen bugs closed with resolution ERRATA?
The page BugZappers/BugStatusWorkFlow displays the work flow which applies to a Fedora bug. However, no policy is given about reopening a closed bug. At the bottom of the page, the reader is referred to "A Bug's Life Cycle" for further information. Here, we read "CLOSED This bug fix has been resolved by the Assigned Engineer. The CLOSED state includes the resolution field which describes why a bug report is closed. See Resolution descriptions. If the CLOSED resolution ERRATA is set, the bug report cannot be reopened. Instead, enter a new bug report for a new problem." The expression "cannot be reopened" is ambiguous. Now, some of my bugs closed with resolution ERRATA have been reopened by other users. Is this procedure allowed or should indeed a new bug be created instead which is what I was doing in the past? ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
