On 5/22/11 10:13 AM, Thomas Kahle wrote: > I like it. Funnily It digged up some stable bugs from the stone-age > that have been processed, but x86 was still on the CC-list.
Thanks. Those old bugs being displayed was a bug, I fixed it. > Have you seen app-portage/tatt ? I think there is a huge overlap between > your project and tatt. Yeah, the project was in fact inspired by tatt and the earlier gatt. > tatt can already fetch bugs from bugzilla, > create USE-flags and reverse dependency, as well as cvs commit scripts. > You can use your own templates for the scripts, but tatt also provides > some. One of the main things I wanted was being able to see all bug comments, bug dependencies, related bugs, and repoman output in the bugzilla viewer. Can tatt do that? I think I'm going to either re-use or copy tatt's parts responsible for compiling and committing the changes. For now I just focused on the first part of the workflow (identifying bugs to work on, and identifying possible problems as early as possible). > Regarding the work-order I intentionally try to be agnostic. I do > security bugs first, and then work on the oldest bug. Right, but sometimes there are bugs with no input from the maintainer. Another thing I'd like to do is to mark such a bug as ignored, or even "ignored until the next update" (e.g. when someone replies on that bug).
signature.asc
Description: OpenPGP digital signature
