Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Enhancement]: Create release channels again #79

Open
falk-w opened this issue Apr 11, 2023 · 2 comments
Open

[Enhancement]: Create release channels again #79

falk-w opened this issue Apr 11, 2023 · 2 comments

Comments

@falk-w
Copy link

falk-w commented Apr 11, 2023

What changes would you like?

It would be nice to have a release channel again as we had in 3.7

See:
channels:
latest/stable: 3.10.1 2023-02-18 (372) 11MB classic
latest/candidate: ↑
latest/beta: ↑
latest/edge: 3.11.1 2023-02-18 (376) 12MB classic
3.7/stable: 3.7.0 2021-09-16 (353) 11MB classic
3.7/candidate: ↑
3.7/beta: ↑
3.7/edge: ↑
3.6/stable: 3.6.3 2021-07-14 (350) 10MB classic
3.6/candidate: ↑
3.6/beta: ↑
3.6/edge: ↑
3.5/stable: 3.5.4 2021-04-15 (336) 9MB classic

It would allow to limit snap upgrades to a certain max version.

Any extra information?

No response

@soumyaDghosh
Copy link
Member

@jnsgruk Is it possible with our new CI? Like dev channel in sublime?

@jnsgruk
Copy link
Member

jnsgruk commented Sep 29, 2024

Yeh it's definitely possible - it's just a fair bit of maintenance to open the new tracks etc.

In general the clients remain pretty backward compatible, and I'm not sure there is a an advantage to a new track for every release.

It is now possible to install particular revisions, which are tied to versions per the tags in this repo?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants