> In my discussions with other developers, I've found that this is the > biggest concern. Most devs are runnning ~amd64, so they don't feel that > they can mark things stable.
W hat about running a stable chroot? Are there any tools that can be used to automate this process? On Wed, Dec 13, 2017 at 12:51 PM, William Hubbs <willi...@gentoo.org> wrote: > On Wed, Dec 13, 2017 at 01:22:04PM +0100, Thomas Deutschmann wrote: > > On 2017-12-12 19:24, Rich Freeman wrote: > > > As far as I'm aware the standing policy already exists that > > > maintainers can stabilize their own packages on amd64. > > > > That's right but keep in mind that nevertheless you need a stable > > system. Marking a package stable because it works on your ~arch box you > > use for your daily dev work would lead the whole process ad absurdum. > > In my discussions with other developers, I've found that this is the > biggest concern. Most devs are runnning ~amd64, so they don't feel that > they can mark things stable. > > > And in general maintainer stabilization should be the last resort. The > > person who wrote the ebuild maybe doesn't notice that the ebuild is > > doing something wrong (doesn't honor CFLAGS, calls compiler directly, > > not working with /bin/sh not /bin/bash ...). > > In theory, this is correct. However, when maintainers don't stabilize > packages and no one else does either, our stable tree suffers. > > William > -- Regards, [image: Visit online journal] <https://lramage94.github.io/> *Lucas Ramage* / Software Engineer ramage.lu...@openmailbox.org / (941) 404-6794 *PGP Fingerprint* / Learn More <https://emailselfdefense.fsf.org/en/> EAE7 45DF 818D 4948 DDA7 0F44 F52A 5A96 7B9B 6FB7 <https://pgp.mit.edu/pks/lookup?op=get&search=0xF52A5A967B9B6FB7> *Visit online journal* http://lramage94.github.io <https://lramage94.github.io/> [image: Github] <https://github.com/lramage94>[image: Linkedin] <https://www.linkedin.com/in/lramage94>
