0neGal

> Why bothering creating GitHub, Thunderstore Stable or Unstable channels, when we can just fetch all available versions from Thunderstore and let users choose themselves (à-la-Minecraft Launcher, if it still...

> Don't really have an idea so I'll leave it up to you :P > > We're [planning to also do a rolling release "git main" package in the future](https://github.com/R2Northstar/Northstar/issues/309)...

> I'd use `development` over `unstable`, as `unstable` just feels too vague to me. Otherwise seems fine to me ^^ The idea is rather to really empathize that it's not...

> Maybe combine the two words and use `unstable, development`? idk ^^ Considering everything else is a single short word and nothing more, that'd be a very long line... GitHub...

> So turns out Thunderstore only allows `MAJOR.MINOR.PATCH` versioning (c.f.: [thunderstore-io/Thunderstore#634](https://github.com/thunderstore-io/Thunderstore/issues/634)). This means stuff like `v1.9.1-rc1` wouldn't work. I suggest waiting until that is fully sorted, as it would not...

So the `mod.json`'s in the Northstar mods will also have the `v1.9.101` version numbers as well? And no rc suffix anywhere? If so this would be pretty easy to implement...

> I guess the best solution would be to have a "translation function" in Viper that takes the the package type (GitHub, Thunderstore stable, Thunderstore unstable) and returns the translated...

Just to clarify, both the Thunderstore version, and the `mod.json` files will all have `v1.9.101` in them when it's an RC build? And if there's more than one build it...

> No, as stated before that's kinda difficult to implement with our CI and would mess with other things, see [#142 (comment)](https://github.com/0neGal/viper/issues/142#issuecomment-1183584130) :P Right, brain bad, and I forgot lol,...

> > If we get over 9 releases, how would we reliably detect whether to replace it with `0`, `1` and so on... > > You mean passing `9` on...