On Sun, May 1, 2016 at 9:32 AM, Jeroen Roovers <j...@gentoo.org> wrote: > And it means we're missing opportunities where "pure" interpreted > packages may test corner cases of the language implementation and find > bugs in (JIT or previously) "compiled" code. And that means we're > calling things "stable" that may expose such bugs that turn out not to > be corner cases at all and affect running systems in unpleasant ways.
While this is a risk, I still think the cleanest solution here is to encourage maintainers to be aware of the packages they maintain and exercise the appropriate discretion when they think these corner cases exist and are important. Understanding the nuances of a package and how it works and how it is used is really a core purpose of having a maintainer in the first place. Of course no maintainer is perfect, but I think the upside is more than the downside here and as with anything we'll learn. -- Rich
