Describe the problem
Currently we suffer from a lot of bugs being introduced into the codebase because we can't reliability test the dev builds before we cut a release.
Describe the solution you'd like
I would like to offer solution to this which is having release channels.
Basically have a Dev/Nighty/Canary/Prerelease (or something quirky maybe) channel that users and devs can opt into to get the latest dev builds of Sable and basically beta test it before we actually make a stable release.
I think this should be a option in the settings.
On how we would go about it, there are several methods but the easiest would be a subdomain like dev.app.sable.moe as long as localstorage and other settings can be shared between the two channels.
Another would be path or cookie based where we serve different versions of Sable depending on those states from server side.
But I'm open to other suggestions for the implementation.
Also I think we should have a pre release in releases for this new channel that automatically gets updated on push to dev branch. This will be mostly for #88
Alternatives considered
We do currently have a dev preview link on cloudflare that automatically gets updated on push to dev that we can use but it's annoying to use due to being on a cloudflare domain and the fact that is isolated from app.sable.moe and not integrated at all, which adds friction to use.
Additional context
The idea is that maintainers and the community can help test out the latest features to find bugs and provide feedback so we can fix them before they end on stable releases. And if something is really broken, easily be able to switch back to stable builds.
Describe the problem
Currently we suffer from a lot of bugs being introduced into the codebase because we can't reliability test the dev builds before we cut a release.
Describe the solution you'd like
I would like to offer solution to this which is having release channels.
Basically have a Dev/Nighty/Canary/Prerelease (or something quirky maybe) channel that users and devs can opt into to get the latest dev builds of Sable and basically beta test it before we actually make a stable release.
I think this should be a option in the settings.
On how we would go about it, there are several methods but the easiest would be a subdomain like dev.app.sable.moe as long as localstorage and other settings can be shared between the two channels.
Another would be path or cookie based where we serve different versions of Sable depending on those states from server side.
But I'm open to other suggestions for the implementation.
Also I think we should have a pre release in releases for this new channel that automatically gets updated on push to dev branch. This will be mostly for #88
Alternatives considered
We do currently have a dev preview link on cloudflare that automatically gets updated on push to dev that we can use but it's annoying to use due to being on a cloudflare domain and the fact that is isolated from app.sable.moe and not integrated at all, which adds friction to use.
Additional context
The idea is that maintainers and the community can help test out the latest features to find bugs and provide feedback so we can fix them before they end on stable releases. And if something is really broken, easily be able to switch back to stable builds.