MicroCloud new tracks request

store-requests
1

Hello,

We’ll be releasing MicroCloud 2.1.0 LTS, which will be the start of the new 2.x series and so will need a 2 track created.

Additionally we will be archiving the previously released revision in latest/stable to a 1/stable channel and so will need a 1 track created.

Finally after our 2.1.0 LTS release we will start new feature releases into the 3.x series and so will need a 3 track created.

So to summarise, please can we have 1, 2 and 3 tracks created.

Thanks!

2

Hi, @tomp !

Could you clarify the snap name(or id), where you would like to create tracks? Is this Install MicroCloud on Linux | Snap Store ?

Thanks, Alex

3

Thats the one thanks!

1 Like
4

Hello again, @tomp !

Per Process for aliases, auto-connections and tracks 2, we need a 1-week voting/discussion period, so I’ll check back on the discussion and votes in a few days.

I have a question before casting my vote:

  • Is there some commitment on maintenance of old versions? e.g. is 1.x still supported with security updates? will it continue to be supported now that 2.x is out, and for how long?
5

Yes we are transitioning away from latest track and will be putting the old stable into 1/stable for archive purposes. Then 2/stable will be new LTS and 3/stable will be for new development releases and will become the next LTS.

1 Like
6

Hey, @tomp ! Thanks for the explanation! I suppose in this case it seems reasonable to follow a simplified version of the process.

I’ve just created tracks 1, 2 and 3 for the snap microcloud.

Enjoy the rest of the week!

1 Like
7

I’d suggest getting those tracks set up ASAP so everything’s in place for the new versions. It’ll make things easier when the feature releases start rolling in for 3.x.

1 Like