On Mon, Nov 22, 2010 at 12:56 PM, Dan Halbert <[email protected]> wrote: > On Monday, November 22, 2010 11:39am, "Matti Airas" <[email protected]> > said: >> http://developer.qt.nokia.com/wiki/PySide_Error_Management > > This sounds nice to me, as the current process is obviously quite opaque. My > bugs have been fixed pretty quickly so far, so I can't complain. But seeing > the priority would be helpful to me to plan whether I need to develop a > workaround for my problem, etc. > > One thing that would be nice: Usually the only comments that show up by the > maintainers in Bugzilla are the commit changeset numbers. I like to know the > details of the fix. It would nice if the changeset references were actual > links, as tracking them down in gitorious is a bit tedious. And/or perhaps > the changeset comments could be included. Hopefully these enhancements could > be done automatically. Either would make the Pyside bugzilla database a bit > more useful in giving information about a fixed bug.
In think there are two ways to improve this: A) setup some sort of "post-commit script" that looks for "Fixes #NNN" in commit messages and add a comment to that bug with the commit link/details B) Have bugzilla itself translate commit hashes into URLs like http://qt.gitorious.org/pyside/pyside/commit/af9b887b1ee894b92c45a91592e9ed3a5f943299 IIRC Mozilla bugzilla does something similar to (A). (B) would be rather easy to implement (bugzilla does that already for things like "Bug #NNN" or "comment #N"), but there might be some issues with identifying the tree for the commit, unless there is some convention, (e.g. using "<project>/<COMMIT_ID>") My two cents, -- Anderson Lizardo OpenBossa Labs - INdT Manaus - Brazil _______________________________________________ PySide mailing list [email protected] http://lists.openbossa.org/listinfo/pyside
