Quoting Paolo Bonzini (2014-02-18 07:53:33) > Il 18/02/2014 13:44, Andreas Färber ha scritto: > >> > There isn't really a standard criterion. It's up to each maintainer to > >> > be stricter or looser on what goes to stable. > > The criteria is pretty simple: Was the breakage in the last release > > already or was it introduced only intermittently. > > You haven't defined breakage; what breakage deserves a change in a > stable release. Some interpret it as regression, some as "any bug", > some as "any crash bug", and so on.
Personally I think it's fair to punt that determination to the stable maintainers: if it's a bug that existed in a previous release, however minor, and you or someone else cares enough to cc: qemu-stable about, it's a reasonable *candidate* for consideration. Factors like whether it breaks guest ABI, migration compatibility, is too risky a backport, etc, should be considered, but if unsure it's fine to punt to stable and let the filtering happen there. If it's rejected/problematic stable should provide a response/reason and the discussion can go from there. Perhaps this may need to be revisited in the future if traffic to qemu-stable becomes unwieldly but I don't think we're there yet. > > Paolo
