LTS Backports Maverick EOL

[Tim Gardner]

On 04/11/2012 06:28 AM, Andy Whitcroft wrote:
> As Maverick is now officially EOL we will no longer be producing further
> kernel updates for that release.  This wil orphan any consumers of the
> LTS Backport Maverick kernel for Lucid.  The security team is recommending
> we migrate them to a later LTS backport kernel.  I tend to agree it does
> not seem appropriate to just leave them silently with no further updates.
> This leaves the question as to where they should be migrated to.  Any jump
> to a later kernel is going to be risky.
> 
> If we are going to jump them to a later LTS backport with the inherant
> risks it likely makes sense to jump them to the latest LTS backport that
> exists for their release to gain them the maximum support and prevent
> us having to do the same again in six months when the following backport
> drops from support too.
> 
> I have a patch in my tree to jump them forward assuming we agree on
> where they should go.  I propose Oneiric.
> 
> Comments?
> 
> -apw
> 

I think automatically updating to another kernel release is likely more
dangerous then not having security patches applied.

What about changing the Maverick kernel meta package reference to point
at a script that asks the user what they wanna do ?

rtg
-- 
Tim Gardner tim.gardner at canonical.com