On Thu 11-Jun-2009 at 11:26 +0200, Yuval Levy wrote: > >AFAIK you're the only person who works consistently through the >trackers. Others, including me, look occasionally at it. Do you see ways >how we can help you maintain the tracker better? should we codify the >process of tracker maintenance?
Yes that would be good, especially because I'm finding that I don't have time to cope with it. Your description is more-or-less what I already do, reports are generally: - duplicates of known bugs - don't have enough information, usually anonymous - something new I usually try and close/score or set to pending, assign the component (enblend/hugin/etc...) and the OS (but only if relevant, a generic bug will get lost if mis-assigned to an OS). Anonymous bugs with not enough information should always be set to pending so the tracker can automatically close them after a few days if there is no more info forthcoming. Also rename the bug, especially if there is a distinctive error message, "stitching fails" almost guarantees that nobody will look at the report. Dealing with duplicates is difficult since searching the tracker is painfully slow. So there are large numbers of duplicates in the tracker, and there are a lot of unclosed reports for things that have since been fixed. So the tracker needs three kinds of maintenance: 1. Triage, described above. We don't really need to log this, just open all the most recent reports and it is fairly obvious when you get to stuff that has aready been dealt with. 2. Cleaning up old stuff, the tracker is a bit of a mess. 3. Actual bug fixing. -- Bruno --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx -~----------~----~----~----~------~----~------~--~---
