Hi list,
We've so far used an ad-hoc process for maintaining bugs in the PySide
Bugzilla. Although the bugs have been fixed at a nice rate of 5-10 bugs
per week, the current system has a few issues. To help fix them, we've
drafted an error management process for PySide.
We hope to tackle the following issues with the process:
- Improve visibility towards bug reporters. Currently, bug reporters
rarely get any feedback until the bug is fixed.
- Clarify the core dev team internal responsibilities.
- Make bug prioritization explicit. Currently, we have our own backlog
prioritization but that isn't visible to the bug reporters.
- Make sure no bugs are left dangling forever.
I have described the planned guidelines on the wiki:
http://developer.qt.nokia.com/wiki/PySide_Error_Management
Basically, whenever a bug comes in, it's evaluated and prioritized, and
whenever something happens to it, that will be reported in Bugzilla.
That's about it.
Despite my loud objections, the team voted me to be the error manager
(EM). Unless anyone finds major issues in the proposed new system, we'll
begin using it more or less right away.
I also intend to assign any bugs belonging to the community members
(packagers, etc.) directly to the respective people. I hope this is all
right. Obviously, those bugs won't be prioritized by me: the maintainers
are free to do it themselves according to their own preferences (or just
ignore the whole thing).
I'd be happy to hear comments on the planned process.
Cheers,
ma.
_______________________________________________
PySide mailing list
[email protected]
http://lists.openbossa.org/listinfo/pyside
