Create versioning startegy for DSS snap

[misohu]

Why it needs to get done

By registering the snap on snapstore we have automatic snap builds from default branch into edge track for free. The question is how are we going to face different versions of snaps?

What needs to get done

Design and implement versioning strategy and CI for DSS snap.

When is the task considered done

Versioning strategy is specified and implemented.

[syncronize-issues-to-jira]

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5474.

This message was autogenerated

[misohu]

After talking to @kenvandine the way how to maintain multiple tracks with different versions is following (the way how the other teams are doing it):

1. We will create a mirror of our git repository in the launchpad which will be in sync with all the changes.
2. In the launchpad we will setup snap builds which will be bound to branches for expected tracks in snapstore.

There is no easy way to do it directly from github.

I was also talking with @DnPlas about possible alternative where we will just keep the build from default github branch to edge and from there we will be just manually creating tracks for different versions. The downside of this is that if we want to fixes from previous versions of dss we just dont have a simple way to fix it in branch and build from that release branch (as it is always built from main).

[andreeamun]

Hello. We will have 0.x versions until further notice and decision. The N-1 support means really 0.x & 0.x-1 in terms of versioning.