On Mon, Jan 11, 2010 at 17:57, Brian Curtin <brian.cur...@gmail.com> wrote:
> On Sun, Jan 10, 2010 at 14:25, Brett Cannon <br...@python.org> wrote: > >> * any changes needed to the issue tracker to help with the workflow? >> (stage field seems like a failed experiment and we now have several >> effective triage people who can help w/ guiding changes) >> >> -Brett >> > I think it would be interesting to see how people are using the tracker, or > how they want to be using it. For example, there are currently over 1500 > open issues with no stage set, some of which seemingly haven't been read by > anyone at all. Would a properly set stage field save issues from falling > into a black hole? > > "Using" is the key word there. I know this thread went on about how bugs tend to end up being left open, but what I was proposing to talk about was whether there is any shift desired by the seasoned tracker users to help in their work. For instance, the Stage field was meant to help, but I don't think it is really getting used much, which makes it at best just a UI junk and at worst something to confuse new users. So I just wanted to discuss things as a group to see if we could streamline some things, add others, etc. At worst I will try to grab people like Mark D., R. David, Antoine, Georg, etc. at the summit (not sure exactly which the heavy bug closers will be there), take them aside, and flat-out ask what they need to make their jobs easier. -Brett
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
