-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 22/05/2011 09:13 ??, Thomas Kahle wrote: > Hi > > On 18:44 Sat 21 May , "Pawe? Hajdan, Jr." wrote: >> Recently there was a discussion about better tools for arch teams, to >> speed up stabilizations and make them less error-prone. >> >> Here's my answer to that, still in very early development: >> <http://git.overlays.gentoo.org/gitweb/?p=proj/arch-tools.git;a=summary> >> >> You can just launch it like this: >> >> ./bugzilla-viewer.py --arch x86 > > 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. > >> It has more options, and can even try to do the stabilization in cvs >> tree and capture repoman output (it has to be enabled from the >> command-line, see --help). > > Have you seen app-portage/tatt ? I think there is a huge overlap between > your project and tatt. 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. The next thing would be to clean up a few bugs and do a release, > unfortunately I have not yet found the time for this. I'd be happy to > give you access to the git-tree your you can just clone it on github. > > https://github.com/tom111/tatt > > I also use aliases like > x86bugs='bugz search --cc x...@gentoo.org -a x...@gentoo.org' > secbugs='x86bugs | grep security' > >> I think the key thing for arch teams is batching. Compilation takes >> time, viewing web pages has latency, so we should maximize the work that >> a developer can do within his limited time. To do that, we should >> prepare as much information as possible up-front (this is the goal of >> bugzilla-viewer.py). > > Regarding the work-order I intentionally try to be agnostic. I do > security bugs first, and then work on the oldest bug. > >> Then the developer can quickly process the list of bugs, and decide what >> he's going to test. And then we can have tools for batch-testing, >> batch-committing, and so on. Some of them already exist. >> >> Patches welcome, and please let me know what you think! > > > Thanks for sharing your scripts. I would prefer to have a single script doing everything, instead of multiple scripts here and there. I would also like to see a minimal webpage ( under http://www.gentoo.org/proj/en/base/tools? ) which would describe how to use these tools on daily basis to deal with the bug workload. That will help the rest of us integrate your scripts to our workflow and be more efficient.
Regards, - -- Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iQIcBAEBCgAGBQJN2NhoAAoJEPqDWhW0r/LCu0MP/AqRaW5FvHEIF2Ixb60atDj9 CJ/hCvFer8aWoo7ckkhWIQTlW7tYwRAgVj3H/rltx/olSEm7aMxqpH1W0VwrB8pU 8Vobec/lme5aBYIqbsnGyqyp2myZ8He53mFj5jb8zwC8J5k6dxJTO5VOzdsC5b5z cL6mJImQjNuyeF5YjfGbXhMxDNIrAe9ckGepiQLXjTp2Hn0YOJqQEI04WMmusZ3w 9SLqJ2s5n8puLIbwKZ4cNvwjilMD4xBuBT6zzMZ4kFWZhgDjY0Cqo9mF9g+kcp0j YiIvFS63+59007UKthwHAurg/8gzE6PLQnMG6hna031b+92RzFEeQVKW/W/AyOSS a92WdbrThyyYsiokmNv6w1aq2UlDNKbbdqVzaNw/xtm0ry3CkbVy0YPalySAAzYs UV7C8pdiwkJnhI+yibg6X19GLoPQvPPR9+3+pwqxoIhkfF9lIv2zBcHBbiRlteF/ 9GJBN+jfRVwW1UDgAT6BAhv0UULaYg+ZPABWj77JKO4wGz/zqonYCzEC7tUeN30U Yo8KQPrXDL5QxAVE7CSHFORRuXCSKdiCfWy9cbeszSLizHJBUB5NQa2UCxura5Ib NaCCGMa0eI3EQFMzxsoEY0MNgkwXZGJk0cKXSR54YxG2tn1PXUV0jGWBunt3qd05 Vx7Dzd7svvyPRco45s3l =S9dR -----END PGP SIGNATURE-----
