xlnx-config has no existing tracks, so per Process for aliases, auto-connections and tracks , we need a voting/discussion period, so I’ll check back on the discussion and votes in a few days.
I have a few questions before casting my vote.
- What’s the release cadence, how often is a new version (potentially requiring a new track) released? is this documented somewhere by upstream? Does this depend on e.g. a new Ubuntu release coming out, with a presumably new kernel?
- Is there some commitment from upstream on maintenance of old versions?
- Can you provide some detail as to why 1.x is only compatible with 20.04 and 2.x only compatible with 22.04? Do they depend on kernel features? would it be feasible to use bases instead, so e.g. 1.x can use
base: core20 and be installable on 22.04-based systems?
I think in general I understand your use case, and given that xlnx-config is somewhat closely tied to hardware, which in turn means a specific kernel, which further points to it heavily depending on which kernel the system ships, I’m mostly OK with granting the track, as we have seen this pattern and there’s precedent for doing things this way.