Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #209757

Re: kernel policy vs bug handling (how to followup #919227 ?)

From Andrea Borgia <andrea@borgia.bo.it>
Newsgroups linux.debian.user
Subject Re: kernel policy vs bug handling (how to followup #919227 ?)
Date 2019-06-08 16:10 +0200
Message-ID <y6KcG-5eQ-7@gated-at.bofh.it> (permalink)
References <xGnln-4CK-9@gated-at.bofh.it> <y6GC6-344-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Il 08/06/19 12:18, Andrei POPESCU ha scritto:

> On Mi, 27 mar 19, 21:22:18, Andrea Borgia wrote:
>> 2) maybe I am not using the proper keywords but I can't seem to find
>> information on Debian kernel policy, specifically: when does a new kernel
>> from upstream enter "unstable"?
> 
> Usually quite soon after the upstream kernel is released as "stable".
> 
> During the freeze only packages meant for the next stable should be
> uploaded to unstable (as per Release Team policy), so new versions might
> go to experimental or not be packaged at all until after the release.

"Unstable" still has 4.19 whereas 5.0.x and 5.1.x are marked as stable 
upstream, so I guess we'll see them in the next release.

Thanks,
Andrea.

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

kernel policy vs bug handling (how to followup #919227 ?) Andrea Borgia <andrea@borgia.bo.it> - 2019-03-27 21:30 +0100
  Re: kernel policy vs bug handling (how to followup #919227 ?) Andrei POPESCU <andreimpopescu@gmail.com> - 2019-06-08 12:20 +0200
    Re: kernel policy vs bug handling (how to followup #919227 ?) Andrea Borgia <andrea@borgia.bo.it> - 2019-06-08 16:10 +0200
      Re: kernel policy vs bug handling (how to followup #919227 ?) Andrei POPESCU <andreimpopescu@gmail.com> - 2019-06-09 09:30 +0200
        Re: kernel policy vs bug handling (how to followup #919227 ?) deloptes <deloptes@gmail.com> - 2019-06-09 22:30 +0200

csiph-web