Sticky stable update channel

[MorrisJobke]

We just had a request by @tessus (nextcloud/updater#159) to provide the admin a channel that allows to stay on the installed major release.

I guess that makes sense to provide. It would then only switch to the next major release at the EOL of that release. It would also allow people to stay on a version if they know that the next major release still has a bug, that they experience but still want to have a maintenance release.

Basically then something like old-stable (ideas for names are welcome) which provides as of now following releases:

• on a 10.0.x instance: 11.0.7 (because 10 is EoL)
• on a 11.0.x instance: 11.0.7
• on a 12.0.x instance: 12.0.5
• on a 13.0.x instance: 13.0.0

@nickvergessen @jospoortvliet @rullzer Opinions about this?

[rullzer]

Yes makes sense. As we want as many people as possible to use the updater adding a channel like this seems like a logical step.

[tessus]

Thank you for taking this into consideration.

As for naming suggestions: how about locked-release, since the channel is locked to the currently installed release.

[nickvergessen]

maybe that can finally be the difference between stable and production 💃

[MorrisJobke]

maybe that can finally be the difference between stable and production 💃

That would not make sense ... production should be updated more early IMO. (with .2 or .3 like we do it right now - only messed up during the 11 -> 12 transition).

[Nils160988]

For me as a user, the difference between stable and production has always been somewhat unclear, so I would support @nickvergessen
So, the chanels would become more similar to the way of debian/ubuntu. You can either choose the stable/beta branch or you can use the codename of a specific branch.

[rullzer]

Maybe we just do this kind of like how docker allows you to do tags?

So there are stable tags:

• stable11 => latest stable version of 11
• stable12 => latest stable version of 12
• stable13, stable => latest stable version of 13

We can then do the same for the beta channel.
When we have the EOL flag in the updater we can anyways signal people they are running a version that is EOL.

We could even do the same for production channels if needed?

This has the advantage the behavior is explicit. And admins probably quickly understand it.

[MorrisJobke]

I would avoid to create a ton of new channels. The idea of this is to have one additional channel and not an overcomplex tagging system. This additional channel has then the characteristic to keep you on the same version (until EoL) - nothing more and nothing less.

[rullzer]

ok fair enough. Lets just do that then. And think about more complex stuff is a need arises.

[MorrisJobke]

Once we have this it should also be added to the description section of the channels: #8815

[tessus]

@MorrisJobke any update on this?