On Mon, Mar 14, 2016 at 12:47:25PM +0100, Phil Sutter wrote:
So far my idea of maintaining Fedora's iproute package was to do
version updates only in Rawhide and backport patches selectively to
stable versions on behalf of bug reports.
But since stable versions indeed receive full kernel updates (not just
backported patches), there is an understandable amount of frustration
amongst users when the shiny new kernel that comes with e.g. F22
provides features userspace does not support.
Especially since upstream iproute2 does not really have a concept of
stable versions, I'm in a bit of a dilemma here: update to keep in sync
with the kernel or not update to not unnecessarily destabilize the
Any comments/advice are highly appreciated.
I have been asked by various people why I don't update iproute in stable
releases to match the shipped kernel version and then had a longer
brainstorming with Lubomir about how to limit the involved risks.
My plan is to indeed do the updates, but I will adjust karma thresholds
to very conservative values for them. I'm thinking about having a stable
threshold of 10 and and unstable one of -1 to enforce a longer review
time and have the process fail early in case problems occur.
Please drop me a note if you have strong feelings against this.