Not requiring SRU changes to be in $current-stable to go in the LTS

[Brian Murray]

On Sat, Mar 09, 2019 at 12:26:25PM -0800, Steve Langasek wrote:
> Hi all,
> 
> I broadly agree with Robie.  To add a little further color, I'd say that the
> one hard rule is that we need to make sure the bug is (on track to be) fixed
> in the devel series before we land an SRU.  We should *default* to SRUing
> into later non-LTS releases whenever we SRU into the LTS release, but it's
> counterproductive to make this a hard rule because the SRUer can always just
> wait it out until the interim release in question has EOLed, submit the same
> SRU, and have it demonstrably fixed in all later supported releases without
> doing any more work - but having deprived their LTS users of the fix for
> some months, which benefits no one.
> 
> So I will always ask an uploader to also SRU the fixes to the interim
> releases if I see that they haven't been, because as Robie says, we also
> have made a committment to support these releases.  But I also am unlikely
> to reject the LTS-only SRU if the uploader is unwilling to do the SRU to
> non-LTS on the basis of their cost-benefit analysis.

In the event that an SRU was uploaded to an LTS release and the next
non-LTS release of Ubuntu would you accept the verified SRU into the LTS
release before the non-LTS one?

--
Brian Murray