hey, folks. Hope no-one minds - yesterday I devised a search to identify F18 anaconda bugs in POST, MODIFIED, ON_QA or VERIFIED status that were fixed in existing anaconda builds but missed being closed, went through, and closed most of them. I checked each bug manually, so for cases which looked like it was possible the bug might not be fixed, I used needinfo instead.
That cleaned up 140 bugs or so. If I manage to find time next week I'll go through all open NEW/ASSIGNED F18 anaconda bugs and do some triage on them. if you don't like the sound of that, let me know!
On 11/23/2012 06:30 PM, Adam Williamson wrote:
hey, folks. Hope no-one minds - yesterday I devised a search to identify F18 anaconda bugs in POST, MODIFIED, ON_QA or VERIFIED status that were fixed in existing anaconda builds but missed being closed, went through, and closed most of them. I checked each bug manually, so for cases which looked like it was possible the bug might not be fixed, I used needinfo instead.
That cleaned up 140 bugs or so. If I manage to find time next week I'll go through all open NEW/ASSIGNED F18 anaconda bugs and do some triage on them. if you don't like the sound of that, let me know!
I for one welcome the cleanup!
On Fri, Nov 23, 2012 at 06:30:38PM -0800, Adam Williamson wrote:
hey, folks. Hope no-one minds - yesterday I devised a search to identify F18 anaconda bugs in POST, MODIFIED, ON_QA or VERIFIED status that were fixed in existing anaconda builds but missed being closed, went through, and closed most of them. I checked each bug manually, so for cases which looked like it was possible the bug might not be fixed, I used needinfo instead.
That cleaned up 140 bugs or so. If I manage to find time next week I'll go through all open NEW/ASSIGNED F18 anaconda bugs and do some triage on them. if you don't like the sound of that, let me know!
Thanks!
anaconda-devel@lists.stg.fedoraproject.org