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

Question: Releases are often tagged with -b, why? #33

Open
RGG-jayoung opened this issue Apr 17, 2024 · 1 comment
Open

Question: Releases are often tagged with -b, why? #33

RGG-jayoung opened this issue Apr 17, 2024 · 1 comment

Comments

@RGG-jayoung
Copy link

RGG-jayoung commented Apr 17, 2024

We're curious on the strategy around naming releases with -b. Assuming the -b suffix indicates beta, it is confusing because there is a long list of releases where some don't have the -b while others do. There is no clear indication of a stable, non-beta release. The screenshot below shows some of this.

If you could kindly provide clarification on:

  • What is the difference of a release suffixed with -b vs. a numerical one?
  • Are releases suffixed with -b to be considered stable?
  • Is there a plan where this becomes consistent in the future? SPM will pull in the highest numeric value when things are mixed like this... so it can have a project pull in a lower than intended version.

image

@username0x0a
Copy link

Additionally, Beta submissions on GitHub should be marked as pre-release (in release version details) so that it would also get a fancy, alarming tag to prevent us from using it without attention. 🤔

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