On Thu, Oct 11, 2018 at 1:14 PM Thomas Deutschmann <whi...@gentoo.org> wrote: > > But that's not the point here. The point was to get some attention that > again we have a lacking architecture (net-dns/dnssec-root is not the > only package where ARM arch team is lacking behind) which affects anyone > "trusting" somehow in STABLE keywords.
ARM is not a Gentoo security supported arch. If the ARM maintainers feel that stable keywords make the lives of their users better, and it isn't causing problems for anybody else, I'm not sure why we should be interfering with this. > > If everyone is using ~ARCH and don't care about STABLE keywords, well, > we could save a bunch of time, energy... > Is this costing YOU any time/energy? If not, why do you care? This thread seems to be devolving into another debate about the purpose of stable, and I'm mainly seeing arguments that have come up countless times already. Most of these arguments tend to point out things that are perceived as being wrong with stable as it currently exists. Most of these arguments are probably posted by people who don't even run stable, let alone maintain it. If somebody wants to actually "fix" stable IMO the best way to go about that is to create a proposal for something new that people will get behind. Gentoo tends to move forward by creating new things, not by arguing about what is broken with old things. What solution is even being proposed? Tell devs they're not allowed to work on stable? That doesn't mean that their next thoughts will be "wow, since I'm not allowed to spend 10 hours per week working on something I cared about, I guess I'll spend those 10 hours per week working on something that somebody else cares about." If it makes Gentoo less useful to them personally, they're just as likely to just drop other contributions they make on the side as they look for better solutions. IMO when stable teams create issues for maintainers by not being responsive to bugs then this needs to be dealt with. However, the Council has already allowed maintainers to drop stable keywords when this happens, and I imagine they'd be responsive to dealing with issues that are more sustained. -- Rich
