1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
|
5 |
On Thu, July 22, 2004 2:32 pm, Stuart Herbert said: |
6 |
> On Thursday 22 July 2004 13:55, Kurt Lieber wrote: |
7 |
>> Assuming baselayout has all the arches that folks are currently working |
8 |
>> on, |
9 |
>> that gives us a list of: |
10 |
>> |
11 |
>> x86 ppc sparc mips alpha arm hppa amd64 ia64 ppc64 s390 |
12 |
> |
13 |
> Isn't that list missing the bsd and the macos arches? |
14 |
> |
15 |
>> What is the problem we're trying to solve here? |
16 |
> |
17 |
> a) There doesn't seem to be a definitive list of ARCH's to assign bugs to |
18 |
> (and the list changes anyway). I don't like guesswork. |
19 |
> b) Adding a cc per arch per bug is time consuming and error-prone. |
20 |
> c) There doesn't seem to be a definitive way to file bugs for ARCH's and |
21 |
> marking packages as stable |
22 |
> d) Assigning bugs to 'arch-maintainers@g.o' will result in too much email |
23 |
> for the people who read it |
24 |
> |
25 |
|
26 |
/me dons flame proof suit and stops lurking |
27 |
|
28 |
Some possible solutions to improve this process based on the current |
29 |
practice of CC'ing arch@g.o |
30 |
|
31 |
How about adding a button to the bugzilla layout for users with developer |
32 |
level privs which adds all known archs to the CC: list? |
33 |
|
34 |
Or how about a simple cmdline tool using "dev-perl/WWW-Bugzilla" which |
35 |
takes a bug number and CC's all known archs@g.o |
36 |
|
37 |
Both of these would maintain the desired process but make it much easier |
38 |
for the developer requesting to achieve. |
39 |
|
40 |
- -- |
41 |
Peter |
42 |
peter.westwood@×××××××.uk |
43 |
|
44 |
-----BEGIN PGP SIGNATURE----- |
45 |
Version: GnuPG v1.2.4 (GNU/Linux) |
46 |
|
47 |
iD8DBQFA/9EGVPRdzag0AcURAtz4AJ9cWgXtih4zWbS/AVu1be4GEjCLaQCeMfSw |
48 |
Pl+Y6CH6HDeOmeQAS7uIwso= |
49 |
=c1Fw |
50 |
-----END PGP SIGNATURE----- |
51 |
|
52 |
|
53 |
-- |
54 |
gentoo-dev@g.o mailing list |