On Fri, Sep 10, 2021 at 2:49 AM Joakim Roubert <[email protected]> wrote: > > Hi! > > I was thinking about k3s, and now that the latest stable k3s is a Kubernetes > 1.21 version: > Do we want to have recipes for multiple k3s versions? I'm thinking someone > perhaps wants, say, 1.20 to go with a system with 1.21, while someone else > perhaps wants 1.21 to go with 1.21 components. > And then have a common .inc-file with everything that is not individual for > the versions, and small recipes with the source revision and such for each > version. > What are your thoughts on this?
I've held pretty firm on not having multiple versions of anything in the layer. Multiple providers, yes, multiple versions .. no. It quite simply splits the testing, multiplies the support and is distracting. And honestly, you'll never get any agreement on versions .. I've been there and done that. We don't even like to do that with the kernel in oe-core, but our hand was a bit forced on that front (and arguably the kernel is actually easier to test). For a version of the layer that might be released against a LTS, the plan was to match up a LTS version and "the latest", but for intermediate/non-LTS releases sticking with one is the goal. Bruce > > BR, > > /Joakim > > > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#6768): https://lists.yoctoproject.org/g/meta-virtualization/message/6768 Mute This Topic: https://lists.yoctoproject.org/mt/85503951/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
