Tom Hoffman
2007-03-07 08:28:20 UTC
With the help of the LaunchPad team at Canonical, and some XML
wrangling by Jean-Francois Roche, we've moved the SchoolTool bug
tracker to the Malone ("Bugsy," get it?) system on LaunchPad here:
https://launchpad.net/schooltool/+bugs
LaunchPad continues to improve, and I found the experience of using
Malone to be mostly painless.
More importantly, I spent two days at the recent PyCon sprint cleaning
up and organizing our bugs. Our bug tracker is now far more usable,
and I'm determined to keep it that way.
If you previously stopped entering bugs into the tracker because it
didn't seem like anyone was paying attention to it, or stopped looking
for bugs to fix because it seemed too out of date and crufty, please
give it another chance.
One source of problems was the difference between bugs that have been
fixed in the development branch but not released in the old calendar
branches that are still in Ubuntu. Bugs that are still outstanding in
the *calendar* branch can be found (and filed) here:
https://bugs.launchpad.net/schooltool/calendar/+bugs
One significant improvement is that the bugs are now organized by
tags, so if you have an interest in or skills for certain types of
bugs, you can find them easily by browsing the different tags, like
"i18n" (internationalization or localization problems) or "html" (bugs
that primarily only require HTML skills) or "ie" (bugs in Internet
Explorer). The tagging isn't perfect, since I made up the tags as I
went, but the whole point of tags is that imperfect metadata is better
than none, right?
I set the status of bugs so that only bugs that are actually being
worked on are "in progress," so you can accurately see what needs
attention.
There are a number of bugs that are marked "fix committed" that can
probably be set to "fix released," but I couldn't remember exactly
which would have been in the last alpha release.
--Tom
wrangling by Jean-Francois Roche, we've moved the SchoolTool bug
tracker to the Malone ("Bugsy," get it?) system on LaunchPad here:
https://launchpad.net/schooltool/+bugs
LaunchPad continues to improve, and I found the experience of using
Malone to be mostly painless.
More importantly, I spent two days at the recent PyCon sprint cleaning
up and organizing our bugs. Our bug tracker is now far more usable,
and I'm determined to keep it that way.
If you previously stopped entering bugs into the tracker because it
didn't seem like anyone was paying attention to it, or stopped looking
for bugs to fix because it seemed too out of date and crufty, please
give it another chance.
One source of problems was the difference between bugs that have been
fixed in the development branch but not released in the old calendar
branches that are still in Ubuntu. Bugs that are still outstanding in
the *calendar* branch can be found (and filed) here:
https://bugs.launchpad.net/schooltool/calendar/+bugs
One significant improvement is that the bugs are now organized by
tags, so if you have an interest in or skills for certain types of
bugs, you can find them easily by browsing the different tags, like
"i18n" (internationalization or localization problems) or "html" (bugs
that primarily only require HTML skills) or "ie" (bugs in Internet
Explorer). The tagging isn't perfect, since I made up the tags as I
went, but the whole point of tags is that imperfect metadata is better
than none, right?
I set the status of bugs so that only bugs that are actually being
worked on are "in progress," so you can accurately see what needs
attention.
There are a number of bugs that are marked "fix committed" that can
probably be set to "fix released," but I couldn't remember exactly
which would have been in the last alpha release.
--Tom