1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
- -----BEGIN PGP SIGNED MESSAGE----- |
5 |
Hash: SHA1 |
6 |
|
7 |
On 07/27/2014 09:55 AM, Pacho Ramos wrote: |
8 |
> Today some user on IRC noted that there were some doubts about if |
9 |
> developers are allowed to stabilize packages they maintain when they are |
10 |
> able to test on relevant arches (I guess this would benefit amd64 and |
11 |
> x86 mostly as it's likely more spread). |
12 |
> |
13 |
> If I don't misremember amd64 team allows that, but looks like devmanual |
14 |
> doesn't reflect that yet: |
15 |
> http://devmanual.gentoo.org/ebuild-writing/ebuild-maintenance/ |
16 |
> |
17 |
> Then, I guess we would need a confirmation to fix devmanual and, in |
18 |
> advance, know more about if there is any other arch team allowing it |
19 |
> (x86?) |
20 |
> |
21 |
The current arm team policy is that anyone who tests on arm may mark |
22 |
~arm, but only arch team members may mark things stable. That said, we |
23 |
do have a pretty lax policy for joining our team. |
24 |
|
25 |
Additionally, it should be noted that this policy is not meant to get in |
26 |
the maintainer's way when they truly do know best. If a maintainer were |
27 |
to need to introduce a fix to a config file, or some fix that didn't |
28 |
change any C code or whatever that maintainer thinks truly shouldn't |
29 |
affect compilation on any arch, then I think a stable bump is fine, and |
30 |
avoids undue stress on the arch teams. |
31 |
|
32 |
Thanks, |
33 |
Zero_Chaos |
34 |
Arm Arch Team co-Lead |
35 |
|
36 |
> Of course, developers stabilizing packages should still follow the usual |
37 |
> test procedures as arch teams members will do. |
38 |
> |
39 |
> Thanks a lot |
40 |
> |
41 |
> |
42 |
|
43 |
- -----BEGIN PGP SIGNATURE----- |
44 |
Version: GnuPG v2 |
45 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
46 |
|
47 |
iQIcBAEBAgAGBQJT1R4ZAAoJEKXdFCfdEflKpPwP/jIDWm9GTczCQOopXSuM6EVS |
48 |
R29zcq8vgZJM1PuU3TKZ8CvcQFawrgckEUzMpDwKVo5mbCLKWrqbGbJFzk3jZusr |
49 |
DYcdWe/+XFjcCVoDOe3MazA0SO/VbXiIWhJYy6nqk/Y6VbkTyPaSuZTFuZztuJPf |
50 |
rSTlDQNJJSzY0A3axtqZxRXJsvYxvj54Rw3mGnqXtjhUJrwTurfb6P4qkH5TAPjG |
51 |
EfGqBUzCn9AsBGl8uxnHbBVMiBQWKwdYgg4rTnCYcrL/K3WocN3ix2Lwd+dZGmve |
52 |
fBUlqA2wMakjBlDn/1lb810+eOzXaatIw/BxWiO5RvManq5OEvKiehwjnK6vvC3c |
53 |
G/NsbnlFNRWtQPXVEgoNi/D8+vIidA+agCydAmmFzZOzHDjzbNG33TT6feq5C7fX |
54 |
9dRmc/7+ZcdIPa+GCp9SEOEYF4qW1gMHYMFZi88Urerl3juItIEocXgWIESK/mFS |
55 |
E+vB8lEn/9GXdW8VRULkuHXpJXs/aiMGua58yWGk9D40Dj3sOSnT+4IC3oBD57Im |
56 |
IumIbMQ5BMS5WQDbOoClY8POVOly4UKa/xomYu+upISHXD2TABaFihke85zJAQaQ |
57 |
jFNzBEKfBn11ORcFGMEFmNeIBBcpjaFkK8m/GJNzg8c/aOkDtluchOpfBoOMcSRv |
58 |
EGkEWigXlNv81o72kxS7 |
59 |
=9bCP |
60 |
- -----END PGP SIGNATURE----- |
61 |
-----BEGIN PGP SIGNATURE----- |
62 |
Version: GnuPG v2 |
63 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
64 |
|
65 |
iQIcBAEBAgAGBQJT1R4xAAoJEKXdFCfdEflKMj8P/3diO123jALGUQO29bsvjFaD |
66 |
vo7l/TvE6eXcR5rk6OoyGmHImClVD8t02BQ5xFdhzM0hr0fgOCH/c+/LLICIO6S8 |
67 |
0+gG8agXlBHc81RGJg6CXqDTKYe+hNdZ9s9eZEBDUk15HjPYEheIsijqnY5284bC |
68 |
aIp/yL+aOFOLBnZ0+CHBFncsK8bM/GfJdgAUBo6dd37erqYST9oF7nzxMMsSeiKQ |
69 |
6VuWPe5zyeZfLjKKoJ/JGxCx8VLA9z+f03ybShAl/s/JKyNohCsVQtcjYnWI4oTu |
70 |
LSO2x/mH3KyUcvQbc38T4DssTjeQ0UNudNhSxD+jhZSdJ09jRuBQPIMhX57jeyBK |
71 |
/ERQwBJAFt1pD0cLKbhc0eUo+RJ6Pxye6xXY7ESGjWnPmlXtq+cBfamQApHVc0hR |
72 |
48WR7wz3L9JysLRUR7/suj8qYqvH2I7Fljk1+d4iexZKuab+OOgNikcm1vO/zsVB |
73 |
XXMeXNrHHPmjBq0G2cXGUbNrPwziZVYFK2f9IUtoNSaWlFi4f/3YZdXIs/jwSIDp |
74 |
3XeL1FtiDI4vxGKTrPVmXdtGmVMsqVGPXL+AX5rMrrnRbKydaUc/AaY0U69I5Xkh |
75 |
MSlGv28wBNMgICYNcuzk3+Rpic+WTdo6hbLzp0GqU8JWbYYJqEV+MtbkGtR1d5ut |
76 |
HB2FNyvVUOKJapOVNaK0 |
77 |
=oFlK |
78 |
-----END PGP SIGNATURE----- |