[gentoo-dev] Clarifying if some arch teams allows maintainers to stabilize package on arches they can test

[gentoo-dev] Clarifying if some arch teams allows maintainers to stabilize package on arches they can test

[Pacho Ramos]

Today some user on IRC noted that there were some doubts about if
developers are allowed to stabilize packages they maintain when they are
able to test on relevant arches (I guess this would benefit amd64 and
x86 mostly as it's likely more spread). 

If I don't misremember amd64 team allows that, but looks like devmanual
doesn't reflect that yet:
http://devmanual.gentoo.org/ebuild-writing/ebuild-maintenance/

Then, I guess we would need a confirmation to fix devmanual and, in
advance, know more about if there is any other arch team allowing it
(x86?)

Of course, developers stabilizing packages should still follow the usual
test procedures as arch teams members will do.

Thanks a lot

[gentoo-dev] Re: Clarifying if some arch teams allows maintainers to stabilize package on arches they can test

[Rick "Zero_Chaos" Farina]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/27/2014 09:55 AM, Pacho Ramos wrote:
> Today some user on IRC noted that there were some doubts about if
> developers are allowed to stabilize packages they maintain when they are
> able to test on relevant arches (I guess this would benefit amd64 and
> x86 mostly as it's likely more spread). 
> 
> If I don't misremember amd64 team allows that, but looks like devmanual
> doesn't reflect that yet:
> http://devmanual.gentoo.org/ebuild-writing/ebuild-maintenance/
> 
> Then, I guess we would need a confirmation to fix devmanual and, in
> advance, know more about if there is any other arch team allowing it
> (x86?)
> 
The current arm team policy is that anyone who tests on arm may mark
~arm, but only arch team members may mark things stable.  That said, we
do have a pretty lax policy for joining our team.

Additionally, it should be noted that this policy is not meant to get in
the maintainer's way when they truly do know best.  If a maintainer were
to need to introduce a fix to a config file, or some fix that didn't
change any C code or whatever that maintainer thinks truly shouldn't
affect compilation on any arch, then I think a stable bump is fine, and
avoids undue stress on the arch teams.

Thanks,
Zero_Chaos
Arm Arch Team co-Lead

> Of course, developers stabilizing packages should still follow the usual
> test procedures as arch teams members will do.
> 
> Thanks a lot
> 
> 

- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJT1R4ZAAoJEKXdFCfdEflKpPwP/jIDWm9GTczCQOopXSuM6EVS
R29zcq8vgZJM1PuU3TKZ8CvcQFawrgckEUzMpDwKVo5mbCLKWrqbGbJFzk3jZusr
DYcdWe/+XFjcCVoDOe3MazA0SO/VbXiIWhJYy6nqk/Y6VbkTyPaSuZTFuZztuJPf
rSTlDQNJJSzY0A3axtqZxRXJsvYxvj54Rw3mGnqXtjhUJrwTurfb6P4qkH5TAPjG
EfGqBUzCn9AsBGl8uxnHbBVMiBQWKwdYgg4rTnCYcrL/K3WocN3ix2Lwd+dZGmve
fBUlqA2wMakjBlDn/1lb810+eOzXaatIw/BxWiO5RvManq5OEvKiehwjnK6vvC3c
G/NsbnlFNRWtQPXVEgoNi/D8+vIidA+agCydAmmFzZOzHDjzbNG33TT6feq5C7fX
9dRmc/7+ZcdIPa+GCp9SEOEYF4qW1gMHYMFZi88Urerl3juItIEocXgWIESK/mFS
E+vB8lEn/9GXdW8VRULkuHXpJXs/aiMGua58yWGk9D40Dj3sOSnT+4IC3oBD57Im
IumIbMQ5BMS5WQDbOoClY8POVOly4UKa/xomYu+upISHXD2TABaFihke85zJAQaQ
jFNzBEKfBn11ORcFGMEFmNeIBBcpjaFkK8m/GJNzg8c/aOkDtluchOpfBoOMcSRv
EGkEWigXlNv81o72kxS7
=9bCP
- -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJT1R4xAAoJEKXdFCfdEflKMj8P/3diO123jALGUQO29bsvjFaD
vo7l/TvE6eXcR5rk6OoyGmHImClVD8t02BQ5xFdhzM0hr0fgOCH/c+/LLICIO6S8
0+gG8agXlBHc81RGJg6CXqDTKYe+hNdZ9s9eZEBDUk15HjPYEheIsijqnY5284bC
aIp/yL+aOFOLBnZ0+CHBFncsK8bM/GfJdgAUBo6dd37erqYST9oF7nzxMMsSeiKQ
6VuWPe5zyeZfLjKKoJ/JGxCx8VLA9z+f03ybShAl/s/JKyNohCsVQtcjYnWI4oTu
LSO2x/mH3KyUcvQbc38T4DssTjeQ0UNudNhSxD+jhZSdJ09jRuBQPIMhX57jeyBK
/ERQwBJAFt1pD0cLKbhc0eUo+RJ6Pxye6xXY7ESGjWnPmlXtq+cBfamQApHVc0hR
48WR7wz3L9JysLRUR7/suj8qYqvH2I7Fljk1+d4iexZKuab+OOgNikcm1vO/zsVB
XXMeXNrHHPmjBq0G2cXGUbNrPwziZVYFK2f9IUtoNSaWlFi4f/3YZdXIs/jwSIDp
3XeL1FtiDI4vxGKTrPVmXdtGmVMsqVGPXL+AX5rMrrnRbKydaUc/AaY0U69I5Xkh
MSlGv28wBNMgICYNcuzk3+Rpic+WTdo6hbLzp0GqU8JWbYYJqEV+MtbkGtR1d5ut
HB2FNyvVUOKJapOVNaK0
=oFlK
-----END PGP SIGNATURE-----

[gentoo-dev] Re: Clarifying if some arch teams allows maintainers to stabilize package on arches they can test

[Tom Gall]

[-- Attachment #1.1: Type: text/plain, Size: 1831 bytes --]

As one of the few people working on ARM64 I’m in agreement. 

Sure a bug or two is probably going to pop up on account of the change but in the grand scheme this seems like a good move.

On Jul 27, 2014, at 10:43 AM, Rick Zero_Chaos Farina <zerochaos@gentoo.org> wrote:

> Signed PGP part
> On 07/27/2014 09:55 AM, Pacho Ramos wrote:
> > Today some user on IRC noted that there were some doubts about if
> > developers are allowed to stabilize packages they maintain when they are
> > able to test on relevant arches (I guess this would benefit amd64 and
> > x86 mostly as it's likely more spread).
> >
> > If I don't misremember amd64 team allows that, but looks like devmanual
> > doesn't reflect that yet:
> > http://devmanual.gentoo.org/ebuild-writing/ebuild-maintenance/
> >
> > Then, I guess we would need a confirmation to fix devmanual and, in
> > advance, know more about if there is any other arch team allowing it
> > (x86?)
> >
> The current arm team policy is that anyone who tests on arm may mark
> ~arm, but only arch team members may mark things stable.  That said, we
> do have a pretty lax policy for joining our team.
> 
> Additionally, it should be noted that this policy is not meant to get in
> the maintainer's way when they truly do know best.  If a maintainer were
> to need to introduce a fix to a config file, or some fix that didn't
> change any C code or whatever that maintainer thinks truly shouldn't
> affect compilation on any arch, then I think a stable bump is fine, and
> avoids undue stress on the arch teams.
> 
> Thanks,
> Zero_Chaos
> Arm Arch Team co-Lead
> 
> > Of course, developers stabilizing packages should still follow the usual
> > test procedures as arch teams members will do.
> >

Exactly.

Tom

(CaptHammer / tgall_foo)
arm64 / arm

[-- Attachment #1.2: Type: text/html, Size: 2706 bytes --]

[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 842 bytes --]

Re: [gentoo-dev] Clarifying if some arch teams allows maintainers to stabilize package on arches they can test

[Tom Wijsman]

[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]

On Sun, 27 Jul 2014 15:55:49 +0200
Pacho Ramos <pacho@gentoo.org> wrote:

> Today some user on IRC noted that there were some doubts about if
> developers are allowed to stabilize packages they maintain when they
> are able to test on relevant arches (I guess this would benefit amd64
> and x86 mostly as it's likely more spread). 
> 
> If I don't misremember amd64 team allows that, but looks like
> devmanual doesn't reflect that yet:
> http://devmanual.gentoo.org/ebuild-writing/ebuild-maintenance/
> 
> Then, I guess we would need a confirmation to fix devmanual and, in
> advance, know more about if there is any other arch team allowing it
> (x86?)
> 
> Of course, developers stabilizing packages should still follow the
> usual test procedures as arch teams members will do.

https://bugs.gentoo.org/show_bug.cgi?id=510198

-- 
With kind regards,

Tom Wijsman (TomWij)
Gentoo Developer

E-mail address  : TomWij@gentoo.org
GPG Public Key  : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2  ABF0 95B2 1FCD 6D34 E57D

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]