-
Notifications
You must be signed in to change notification settings - Fork 95
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
Pre-release naming convention #570
Comments
We can't react with those emojis, unfortunately on a few are supported. I'll put two comments below and people can thumbs-up for them. |
🕯 a[0+] |
🔤 rc[1+] |
Ugh so frustrating!!!! @jbteves by the way you switched the emojis. EDIT: I went ahead and changed the vote-mojis just to make the vote more obvious. |
It seems that they can coexist according to semvar:
Still, to reflect common usage I'd agree to adopt one or the other. My vote is for |
Oops, sorry, I missed that @tsalo I'm fine with either, but do think we need to pick one. |
@emdupre, whoa.... yeah let's not have that intense a development cycle. Agreed about adopting one or the other. How about we close the polls on this (since it's not that big of a deal) on Friday? |
Sounds reasonable to me ! |
Okay, the polls have officially closed as of 10:31 pm EDT on July 13. Yes, this is 52 days after when we said the poll would close, but, in fairness, I forgot. Anywayyy... we have a majority vote for the RC system, and we shall adopt it henceforth. |
Summary
Continues from #568 (comment), but separated into its own issue for posterity. We have two competing naming conventions for unstable/pre-releases: alpha (
X.X.Xa[0-9+]
) and release candidate (X.X.Xrc[0-9+]
). In our release history, we have two cases of each: 0.0.5rc1 and 0.0.5rc2 for release candidate and 0.0.9a0 and 0.0.9a1 for alpha.Next Steps
Please vote 🎉 for the release candidate system and 🚀 for the alpha system.
The text was updated successfully, but these errors were encountered: