Can you detail the rationale for requiring this for canonical-livepatch? you said this is about bases, whereas typically tracks with ubuntu release names are used when a different build of the snap is required for different kernel features, typically from the gadget snap. Is there a problem with canonical-livepatch just declaring a base (say core20) and installing that as required on systems?
the primary reason for doing this is user experience and speed. Since canonical-livepatch is usually installed via the ua tool, a lengthy install disrupts the user experience.
The canonical livepatch snap needs to support trusty, so it’s currently built with base core. When it’s installed on bionic or focal, usually the core snap needs to be installed first, increasing the download time significantly.
This especially affects Ubuntu Pro, where UA attachment is part of the init process.
Thanks, I’ve created the tracks as requested by @domas. Let me know if you agree with Igor’s suggestion, in which case I can clear the tracks (before you publish anything to them!) and create ones with the new names. But it’s up to you as requester