The current 3-week Kernel SRU cycle is reasonably responsive but prone to interruptions from urgent CVEs, urgent customer requests and regressions found in -updates or during testing. It is very common for the start of any SRU cycle to be disrupted by these factors and for the cycle to have to be extended. This makes it challenging to deliver some CVE fixes in a timely manner. In order to improve our kernel SRU release cadence velocity and predictability, the Canonical Kernel Team is transition...