On Tue, Dec 15, 2015 at 03:20:06PM +0000, Jóhann B. Guðmundsson wrote: > > > On 12/15/2015 02:48 PM, Josh Boyer wrote: > >On Tue, Dec 15, 2015 at 02:33:48PM +0000, Jóhann B. Guðmundsson wrote: > > > > > >On 11/20/2015 04:13 PM, Josh Boyer wrote: > >>4.3.3 has now been release but no sign of it in F23. > >It won't be submitted until January. We don't want to do a major rebase > >the week before most of us go away on PTO. There is a COPR that > >contains builds from the stabilization branch in Fedora git for those > >that wish to jump early. > > Did not know about that corp repo hence I have to ask... > > Is that the latest stable kernel release ( 4.3.3 ) and will always Not yet. It will be updated to 4.3.3 (or 4.3.4) at some point this week, but 4.3.3 has a known memory leak. > contain the latest stable release ( for all current Fedora releases It won't always even exist. It's temporary. > ) or is it an replacement for rawhide-nodebug and contains the No, it is not a replacement for rawhide-nodebug. It has nothing to do with rawhide. > latest development kernel release ( 4.4 ) which I was informed was > deadlocking in some cases ( which may or may not be resolved in rc5 > based on [1] ) and those that are using Fedora as workstation can > avoid installing ( unless they are doing direct development on the > kernel or testing )? The email I just sent to Matthew has more details on why it exists and why 4.3 is weird. If people using Rawhide Workstation are hitting problems with the rawhide kernel, they should report the bugs. It is also a good idea to keep at least one known good working kernel installed on a rawhide machine, which is one of the main motivations for having 3 kernels installed at a time anyway. One could use this COPR to get a stable kernel I guess, but it would involve manual installation if they're already on 4.4-rcX because RPM would view the COPR builds as older. josh _______________________________________________ kernel mailing list kernel@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/kernel@xxxxxxxxxxxxxxxxxxxxxxx