Skip to content
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

Use a different versioning format #653

Closed
Jan200101 opened this issue Jun 18, 2024 · 6 comments
Closed

Use a different versioning format #653

Jan200101 opened this issue Jun 18, 2024 · 6 comments

Comments

@Jan200101
Copy link

Northstar doesn't really make use of any real versioning format with the version just being incremented as is felt.

I am in favort of adopting some versioning schema already applied to the real work like:

  • semver
  • calver
  • WendtVer
  • GitVer
  • pragmaticversioning
  • even/odd versioning (SDL)
  • ZeroVer
@GeckoEidechse
Copy link
Member

I guess that would apply to all of Northstar and not just launcher, right? ^^

@Jan200101
Copy link
Author

Jan200101 commented Jun 18, 2024

correct, would probably be better in the Northstar repo.
I can't transfer it myself.

@GeckoEidechse GeckoEidechse transferred this issue from R2Northstar/NorthstarLauncher Jun 18, 2024
@GeckoEidechse
Copy link
Member

I think one of the suggestions made somewhere on the Northstar Discord (cannot find it rn) by @F1F7Y was to do like FEATURE.PATCH so like e.g. v82.1, essentially dropping one version number.

@Jan200101
Copy link
Author

I think one of the suggestions [...] was to do like FEATURE.PATCH so like e.g. v82.1 ...

I am in favor of this.

@GeckoEidechse
Copy link
Member

Maybe to give a bit of backstory of how we ended up with something like v1.24.7 is that back in the very very early days of Northstar when we released like v1.4.0 which had a decent refactor at the time, I suggested to @BobTheBob9 just call it a v2.0.0, as I was anticipating the scenario we have rn.

At the time they declined saying there's still a few bigger changes in the works that would warrant a 2.0

From there the idea was to have Frontier Defense release or something similar be the 2.0 but as you can obviously tell, that never released (it'll come soon™).

Given that I'm getting back on track, I'm kinda hoping to just get something out that warrants a 2.0 and from there we just push out MAJOR version bumps more liberally quickly going 3.0 -> 4.0 -> ... until version numbers become less relevant to the average player.

@EM4Volts
Copy link

Given that I'm getting back on track, I'm kinda hoping to just get something out that warrants a 2.0 and from there we just push out MAJOR version bumps more liberally quickly going 3.0 -> 4.0 -> ... until version numbers become less relevant to the average player.

I dont really think players will care about the version number. Sure announcing a 2.0 would be cool and people would look at it i think ultimately people wont really care.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

3 participants