[11:06] <dupondje> Small question. Why does the latest kernel for disco in proposed update to:   * Disco update: 5.0.12 upstream stable release (LP: #1830934)
[11:06] <dupondje> While there is 5.0.21 already, why is there such a delay?
[13:01] <apw> dupondje, because they take time to prepare i guess, and a lot of time consumed by security CRD type releases like the one we just had
[13:02] <apw> dupondje, particularly where those stable updates clash with or contain variants of the CRD patch kits
[13:02] <apw> we normally try and be up to date as close as we can
[13:48] <dupondje> apw: ok thanks! :) 5.0.12 is 7 weeks old.
[13:49] <dupondje> What are those CRD patch kits?
[13:56] <apw> yeah, its not ideal for sure
[13:59] <apw> dupondje, the MDS release last monday for example, getting those ready can delay other work
[14:02] <dupondje> apw: Yea indeed. But you could lower the time by just using the latest 5.0.x (in disco case) kernel (which has the patch included)
[14:02] <dupondje> then you don't need to adjust the patch yourself
[14:02] <dupondje> Anyway, I don't know the whole ubuntu kernel flow :)
[14:03] <apw> we released those kernels before the patch kit was available on stable; necessarily because it was embargoed
[14:06] <dupondje> ah :(
[14:07] <dupondje> lets further debug my curreny issue with 5.2-rc5
[14:08] <dupondje> network seems to drop packages every 5 minutes or so :)
[14:08] <dupondje> 20 drops at ip_rcv_finish_core.isra.22+1ac (0xffffffff96d4828c)
[14:08] <apw> dupondje, we are aware of the tardyness of stable there; and it is on the teams radar