We’ll start the comment/vote gathering process to run until April 18th.
Being consistent with my thoughts in Request core18-3.4 track for ffmpeg-sdk-gplv3 stage snap, I don’t feel tracks are appropriate for “library” snaps. To repeat myself, tracks are meant to “give a group of users the ability to stay on a robust, proven version of their software, even when a newer stable version has been released. Using a track can be useful if the newer stable version has some backward-incompatibilities”. This is not the case with
zenity-integration, I believe, since it’s meant to be included in other snaps; further, it’s unclear to me how a developer would use this zenity-integration and what happens if the
base: requirement for the main snap conflicts with that of the
zenity-integration included snap. Could you provide an example of how I would use
zenity-integration in my snap?
On the plus side, we do use tracks to allow a snap to support two different core versions, in such a case the tracks are typically
I’ll wait to read your reply before casting a vote (and remember, regardless of my vote, we need a +2/-2 by reviewers at the end of the voting period to make a final decision).