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

The last release is 1.1.3 from 5 years ago. #67

Open
iiv3 opened this issue Jan 11, 2025 · 2 comments
Open

The last release is 1.1.3 from 5 years ago. #67

iiv3 opened this issue Jan 11, 2025 · 2 comments

Comments

@iiv3
Copy link

iiv3 commented Jan 11, 2025

You have been tagging new versions, but you were not cutting any releases.

The last release is from 5 years ago.

I tried to compile gzdoom, it failed for missing enum from zmusic.h. When I checked I still had the latest release.

@madame-rachelle
Copy link
Collaborator

Every project is different - with some you have to use the tags. Official releases are sourced from the actual tags and if a tag is not meant to be used in a release it will be marked with some indication of development (i.e. dev, pre, alpha/beta/testing/staging/whatever)

@iiv3
Copy link
Author

iiv3 commented Jan 22, 2025

The problem is the inconsistency.
If there were no releases of any kind, then looking at the tags is the logical follow up.

However if there are (old) releases, it's logical to assume that the project is using that scheme.

I really don't see any downside of using the release functionality of github. It has the added bonus of sending notifications to everybody who follows the project.

I do suspect that cutting release requires some permissions and the person who has them is been out of reach.

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

No branches or pull requests

2 participants