GNOME Bugzilla – Bug 590840
[Stock answers extension] Add a sentence to suggest reporters to verify the bugs
Last modified: 2015-02-24 20:11:08 UTC
Adding additional sentence to stock answers to verify fixed bugs as discussed here: http://live.gnome.org/Bugsquad/Meetings/20090903#head-3a68ed263596276c5344af04e6c8e26bb222653d
Created attachment 139935 [details] [review] Add a sentence to suggest reporters to verify the bugs
Patch looks good to me. OLAV?
Javier, The init open bug statement leads to and Empty page. I like the new stock responses great job. lajjr
Hello Leo, yes, the page has moved to http://live.gnome.org/Bugsquad/Meetings/20090803#head-612aa49b0ca19b71dac7cd0b2e47bb2271db97f5 Thank you for ping me!
I wonder how much sense it is to apply these. This as we're upgrading in less than a wekk.
Can anyone commit this? (I don't have commit permissions)
No, it does not make sense at all currently. See comment 5.
So, we do have a new Bugzilla. Any chance we can have a new patch? :)
(In reply to comment #8) > So, we do have a new Bugzilla. Any chance we can have a new patch? :) Sure, Where is the code of the new Bugzilla?
Javier: On Launchpad: https://launchpad.net/bugzilla.gnome.org
Comment on attachment 139935 [details] [review] Add a sentence to suggest reporters to verify the bugs Code will soon be under bugzilla-gnome-org-extensions/template/en/default/hook/bug/edit-after_comment_textarea.html.tmpl in GNOME Git instead of template/en/default/bug/edit.html.tmpl hence marking as needs-work - should be applied against new location. Further proposals regarding content: * by marking this report => by setting the status of this report * re-open => reopen; plus ask reporter to mention her/his new version?
This will be fixed once we upgrade to Bugzilla 4.4: https://git.gnome.org/browse/bugzilla-gnome-org-extensions/commit/?id=9a961c932d849906086dbe8234d8319037039d93
Meh, wrong link. The right one is: https://git.gnome.org/browse/bugzilla-gnome-org-extensions/commit/?id=c7dc7ea1e1ad7dfc76d819ff67622803d8350677
*** Bug 744207 has been marked as a duplicate of this bug. ***
A sentence requesting verification got added. I consider that harmful. 1. As a maintainer, I really don't want to be spammed with random verifications. For the few I would like verification, I would much rather ask for it explicitly. There's a ~1 year delay involved, at best, when distributions are involved. In almost all cases the bug will be long forgotten by whoever fixed it and I don't see anyone spending time reinvestigating a bug. 2. I am always wary of asking reporters to do pointless work. This work is pointless unless someone is going to act on it. I don't see who would do that. Who is this supposed to benefit? I note that the link allegedly pointing to a discussion about this points to no such thing. Can this be reverted or, alternatively, can module maintainers opt out?
It looks like the git links here are dead too. Someone who thought this was a reasonable idea really needs to step forward.
Git link is now https://git.gnome.org/browse/bugzilla-gnome-org-customizations/commit/?id=c7dc7ea1e1ad7dfc76d819ff67622803d8350677 I put the patch in, Javier proposed it. And I think I slightly tend towards reverting those changes but would like to have Javier's input.
Yeah, I'd be ok with the revertion: AFAIK, no project is using the VERIFIED status anyway. Actually, I'd suggest to remove the VERIFIED status from our GNOME bugzilla instance.
Reverted in https://git.gnome.org/browse/bugzilla-gnome-org-customizations/commit/?h=production&id=e1f41395e4c4932f073e983fef034b8121d6a03b Closing as WONTFIX.