For the freeorion game snap I request a track ‘forum-games’ (or similar named e.g. forum-community).
Our forum community organizes to play the latest working versions (slow games, taking some months) and we support that by providing snaps for that version.
As the game branch might diverge from the latest/beta channel, we are currently pushing out branch channels (latest/beta/slow-game-xxx) for the xxxth forum community game.
This has the benefit that everybody gets the correct version as soon as the server is updated. One downside, which I want to work around using the requested track, is that the branches default back to latest/beta as soon as the branch times out. And if multiple revisions of latest/beta come in, the correct game revision gets rotated out
Depending on how an unset stable branch in a track works the idea is:
- case A (best case): if a branch channel times out and no release in that track is set, the current revision is kept; we simply do not define a stable/candidate/beta revision where the branch may fall back to and local revisions are updated fine and . If something like automated abuse of the snap shows up there is the option to set a revision for e.g. stable in order to fix that (probably that would just show a disclaimer with info what to do).
- case B: we define a dummy revision in e.g. stable and the snap there basically displays a disclaimer; people will usually have still the previous revision on the disk so they can revert The idea is, by having a unchanging ‘forum-games/stable’ revision, that a timed out branch will (usually) keep a local copy of the game revision one can revert to.