9:36 a.m.
Heya,
I was just doing some RDO bug scrub, and as of writing this here's the
current state of affairs:
- NEW, ASSIGNED, or ON_DEV : 138 bugs
- MODFIEID, POST, or ON_QA : 91 bugs
- VERIFIED : 4 bugs
Here's[1] all the bugs, plain text formatted. That's the script I
used[2].
On a related note, next community bug triage is on upcoming Wednesday
(19-MAR-2014), if you have some spare cycles, please join us on #rdo.
[1]
http://kashyapc.fedorapeople.org/virt/openstack/bugzilla/rdo-bug-status/a...
[2] http://kashyapc.fedorapeople.org/virt/openstack/bugzilla/query-all-rdo-bu...
--
/kashyap
3:29 a.m.
On Wed, Mar 12, 2014 at 08:06:10PM +0530, Kashyap Chamarthy wrote:
Heya,
I was just doing some RDO bug scrub, and as of writing this here's the
current state of affairs:
- NEW, ASSIGNED, or ON_DEV : 138 bugs
- MODFIEID, POST, or ON_QA : 91 bugs
- VERIFIED : 4 bugs
As of today, status of RDO bugs[1], 20-MAR-2014:
- NEW, ASSIGNED, or ON_DEV : 135 bugs
- MODFIEID, POST, or ON_QA : 92 bugs
- VERIFIED : 4 bugs
About managing stale bugs, how about this: we could set NEEDINFO on
reporter, and if there's no response in a month (or so?), close the bug
with resolution INSUFFICIENT_DATA. And add a note to reopen the bug if
the reporter can reproduce it again. (i.e. if you file a bug, you are
expected to proactively keep track of it, provide information/test with
new builds. Okay, I admit that's 100% true in only utopian world, but
we can strive to stay diligent. :-) )
Comments/thoughts on this are welcome.
[1]
http://kashyapc.fedorapeople.org/virt/openstack/bugzilla/rdo-bug-status/a...
--
/kashyap
3912
days inactive
3920
days old
1 comments
1 participants
participants (1)
-
Kashyap Chamarthy