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 <[email protected]> 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
signature.asc
Description: Message signed with OpenPGP using GPGMail
