LTS roll-forward policy - small stable core, roll everything else

Situation

Define a small core set of packages (~5) that stay stable in LTS releases (kernel, glibc, gcc, and a few others). Everything else can be rolled forward aggressively. Customer-specific additions can be negotiated as needed.

Reasoning

Most customers only care about a handful of core packages. The rest is false precision that costs significant engineering effort. By being honest about what we actually keep stable vs rolling, we simplify engineering while meeting real customer needs. Can position this positively as guaranteeing stability for the packages customers actually care about.

Additional Context

Discussion about why CIQ has too many LTS versions and struggles to maintain them all. Customers typically care about kernel, glibc, gcc, bind, Apache, and maybe one more package specific to them.

Observed Evidence

"So long as its not a core package... they dont care. If its a node package, we can rebase to our hearts content" and "We actually should go define those. Its a stable core." and Justin identified as best qualified to write this down.

Confidence Breakdown

Reasoning Depth Analysis