1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA512 |
3 |
|
4 |
On 22/05/2011 09:13 ??, Thomas Kahle wrote: |
5 |
> Hi |
6 |
> |
7 |
> On 18:44 Sat 21 May , "Pawe? Hajdan, Jr." wrote: |
8 |
>> Recently there was a discussion about better tools for arch teams, to |
9 |
>> speed up stabilizations and make them less error-prone. |
10 |
>> |
11 |
>> Here's my answer to that, still in very early development: |
12 |
>> <http://git.overlays.gentoo.org/gitweb/?p=proj/arch-tools.git;a=summary> |
13 |
>> |
14 |
>> You can just launch it like this: |
15 |
>> |
16 |
>> ./bugzilla-viewer.py --arch x86 |
17 |
> |
18 |
> I like it. Funnily It digged up some stable bugs from the stone-age |
19 |
> that have been processed, but x86 was still on the CC-list. |
20 |
> |
21 |
>> It has more options, and can even try to do the stabilization in cvs |
22 |
>> tree and capture repoman output (it has to be enabled from the |
23 |
>> command-line, see --help). |
24 |
> |
25 |
> Have you seen app-portage/tatt ? I think there is a huge overlap between |
26 |
> your project and tatt. tatt can already fetch bugs from bugzilla, |
27 |
> create USE-flags and reverse dependency, as well as cvs commit scripts. |
28 |
> You can use your own templates for the scripts, but tatt also provides |
29 |
> some. The next thing would be to clean up a few bugs and do a release, |
30 |
> unfortunately I have not yet found the time for this. I'd be happy to |
31 |
> give you access to the git-tree your you can just clone it on github. |
32 |
> |
33 |
> https://github.com/tom111/tatt |
34 |
> |
35 |
> I also use aliases like |
36 |
> x86bugs='bugz search --cc x86@g.o -a x86@g.o' |
37 |
> secbugs='x86bugs | grep security' |
38 |
> |
39 |
>> I think the key thing for arch teams is batching. Compilation takes |
40 |
>> time, viewing web pages has latency, so we should maximize the work that |
41 |
>> a developer can do within his limited time. To do that, we should |
42 |
>> prepare as much information as possible up-front (this is the goal of |
43 |
>> bugzilla-viewer.py). |
44 |
> |
45 |
> Regarding the work-order I intentionally try to be agnostic. I do |
46 |
> security bugs first, and then work on the oldest bug. |
47 |
> |
48 |
>> Then the developer can quickly process the list of bugs, and decide what |
49 |
>> he's going to test. And then we can have tools for batch-testing, |
50 |
>> batch-committing, and so on. Some of them already exist. |
51 |
>> |
52 |
>> Patches welcome, and please let me know what you think! |
53 |
> |
54 |
> |
55 |
> |
56 |
Thanks for sharing your scripts. I would prefer to have a single script |
57 |
doing everything, instead of multiple scripts here and there. I would |
58 |
also like to see a minimal webpage ( under |
59 |
http://www.gentoo.org/proj/en/base/tools? ) which would describe how to |
60 |
use these tools on daily basis to deal with the bug workload. That will |
61 |
help the rest of us integrate your scripts to our workflow and be more |
62 |
efficient. |
63 |
|
64 |
Regards, |
65 |
- -- |
66 |
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2 |
67 |
-----BEGIN PGP SIGNATURE----- |
68 |
Version: GnuPG v2.0.17 (GNU/Linux) |
69 |
|
70 |
iQIcBAEBCgAGBQJN2NhoAAoJEPqDWhW0r/LCu0MP/AqRaW5FvHEIF2Ixb60atDj9 |
71 |
CJ/hCvFer8aWoo7ckkhWIQTlW7tYwRAgVj3H/rltx/olSEm7aMxqpH1W0VwrB8pU |
72 |
8Vobec/lme5aBYIqbsnGyqyp2myZ8He53mFj5jb8zwC8J5k6dxJTO5VOzdsC5b5z |
73 |
cL6mJImQjNuyeF5YjfGbXhMxDNIrAe9ckGepiQLXjTp2Hn0YOJqQEI04WMmusZ3w |
74 |
9SLqJ2s5n8puLIbwKZ4cNvwjilMD4xBuBT6zzMZ4kFWZhgDjY0Cqo9mF9g+kcp0j |
75 |
YiIvFS63+59007UKthwHAurg/8gzE6PLQnMG6hna031b+92RzFEeQVKW/W/AyOSS |
76 |
a92WdbrThyyYsiokmNv6w1aq2UlDNKbbdqVzaNw/xtm0ry3CkbVy0YPalySAAzYs |
77 |
UV7C8pdiwkJnhI+yibg6X19GLoPQvPPR9+3+pwqxoIhkfF9lIv2zBcHBbiRlteF/ |
78 |
9GJBN+jfRVwW1UDgAT6BAhv0UULaYg+ZPABWj77JKO4wGz/zqonYCzEC7tUeN30U |
79 |
Yo8KQPrXDL5QxAVE7CSHFORRuXCSKdiCfWy9cbeszSLizHJBUB5NQa2UCxura5Ib |
80 |
NaCCGMa0eI3EQFMzxsoEY0MNgkwXZGJk0cKXSR54YxG2tn1PXUV0jGWBunt3qd05 |
81 |
Vx7Dzd7svvyPRco45s3l |
82 |
=S9dR |
83 |
-----END PGP SIGNATURE----- |