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.
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. 🤔
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:
-b
vs. a numerical one?-b
to be considered stable?