Hello
I was thinking it could be nice to have a track called “staging” for my Focus | Project app (https://snapcraft.io/focus-project/), so that I could experiment with look/feel/setup experience altogether, before exposing the potential users to something less worked out.
Not sure if it’s a less ordinary request. If it isn’t a bad idea for some reason, could the track be created? Otherwise I’m all ears for the (public) counterarguments.
Thank you!
Janos
Hello
I was thinking it could be nice to have a track called “staging” for my Focus | Project app (https://snapcraft.io/focus-project/), so that I could experiment with look/feel/setup experience altogether, before exposing the potential users to something less worked out.
Not sure if it’s a less ordinary request. If it isn’t a bad idea for some reason, could the track be created? Otherwise I’m all ears for the (public) counterarguments.
(UPDATE: I’m also interested if there’s any other approach to imitate the “live test” of updates, preferably including actually installing snaps before putting them out available to the general public. I’ve just deployed for now, it’s been long due anyway.
I would still ask for a “staging” track unless discouraged for any reason)
Thank you!
Janos
Hey Janos,
We recommend utilising an existing channel, e.g. edge, rather than creating a staging track. Tracks are intended for separate, longer-lived release lines, while edge is designed for early testing and needs to be installed explicitly with --channel=edge. You can then promote it along the line once you feel comfortable with it.
There are also branch as part of the channel concept, which are intended for short-lived use cases such as hotfixes. They are cleaned up after 30 days without an update, which may or may not suit your purpose.
Feel free to check some example use cases for Snap channels in the Snapcraft channels documentation.
Hope this helps!
Gravity
Hello!
I wasn’t quite sure what I really wanted to ask myself. (Though I do/did try to read the documentation.)
I guess it’s more about “private” builds: say for the developer/team, before any form of release were to reach the public.
No trick here, not for internal, enterprise-wide distributions – the latter I think I’ve seen somewhere to fall more on the proprietary side of Ubuntu, perhaps via a self-hosted store. Much more just internal, but realistic testing.
Item restricted to a few people and maybe only available on the web could also do the job I guess, but I have no idea how you’d prevent such an option from being abused effectively as self-hosting a store.
Anyway, I think I get that it’s not currently a Snap store feature, and probably not in the plans either (and do please correct me if I’m wrong there - otherwise yes, your reply does seem to confirm what I was thinking - thank you!)
(Also I think I’ll be able to sort out my problem in the end in a different way, only a bit later.)
Cheers,
Janos