You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
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.
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.
The text was updated successfully, but these errors were encountered: