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
Please tag unstable releases as pre-release #4874
Comments
Despite its name, an unstable release is still a full release. All software packages except steam are being updated, including the Ubuntu PPA. I see no reason why Nix should reject it. In case you're OK with a special switch for ES, you can rely on the fact that unstable releases always have uneven PATCH versions numbers (0.9.9, 0.9.11 etc). |
Even the Steam release is updated, albeit only for the beta channel, for "unstable" releases. |
Only the beta channel being updated sounds like an indication that this is a pre-release? |
Depends... On steam, it is something akin to a pre-release. For all other package sources (the ubuntu PPA, unofficial windows package repos and debian (#4630) ) it is a regular release. To me, Nix packages would fall into the latter category, rather than the special case steam. |
Tech-savy people that are using something like nixpkgs are probably the sort of people that prefer to have the most up to date content instead of being stuck on whatever the current "official" steam build. I can't speak from experience, but that's what it seems like to me. It is also worth noting that the "beta" / unstable release isn't an experimental side-branch or anything, it is the "soon-to-be-official" release for those who want it a bit faster than they would otherwise get it. It typically has a lot of fixes and improvements over the stable release that preceded it, so I would say it is a clear step up. And for the technically inclined, it is worth noting that all of these are beta releases: We haven't hit version 1.0.0 yet. |
I run a bot that automatically updates software for the Nixpkgs package repository and it uses GitHub releases information to decide to update. It would be helpful to us if you could mark your unstable releases as pre-release in GitHub, so we can filter them out.
https://github.com/endless-sky/endless-sky/releases
https://help.github.com/en/github/administering-a-repository/managing-releases-in-a-repository
The text was updated successfully, but these errors were encountered: