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

Simplify version support #2191

Merged
merged 6 commits into from
Feb 4, 2024
Merged

Conversation

lmoureaux
Copy link
Contributor

When the version system was designed, we envisioned two types of release:

  • Stable releases 3.0, 3.1, 3.2, etc.
  • Pre-releases 3.0-alpha.1 etc.

In addition, we wanted to show a commit id in various places for intermediate builds. The code was written to change the C++ side of things as little as possible, which resulted in some hacks being used. Also, we don't strictly follow this scheme in practice since we publish patch releases to the stable, e.g. 3.0.2.

This PR removes a hack and code we don't need:

  • Support for emergency versions (we just release a new minor if needed)
  • Support for commit SHAs (it was hacky; I can add it back in this PR if deemed necessary, but it will take some CMake gymnastics so I'd prefer a new issue)
  • Some functions that ended up returning the exact same version as we use everywhere

This allows some simplification to the CMake logic constructing the version.
The release documentation is also updated with the new expected tag format (three digits without -stable for stable releases).

This function was bad for translators and not really needed.
It was always equal to freeciv21_version().
It was always equal to freeciv21_version().
When the version system was designed, we envisioned two types of release:
* Stable releases 3.0, 3.1, 3.2, etc.
* Pre-releases 3.0-alpha.1 etc.

In addition, we wanted to show a commit id in various places for intermediate
builds. The code was written to change the C++ side of things as little as
possible, which resulted in some hacks being used. In practice, we don't
strictly follow this scheme since we publish patch releases to the stable, e.g.
3.0.2.

This patch removes a hack and code we don't need:
* Support for emergency versions (we just release a new minor if needed)
* Support for commit SHAs (it was hacky)

The release documentation is also updated with the new expected tag format
(three digits without -stable for stable releases).
@lmoureaux lmoureaux requested a review from jwrober February 4, 2024 03:55
@jwrober jwrober merged commit ddda37f into longturn:master Feb 4, 2024
21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants