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

Pre-release naming convention #570

Closed
tsalo opened this issue May 15, 2020 · 9 comments
Closed

Pre-release naming convention #570

tsalo opened this issue May 15, 2020 · 9 comments
Labels
question issues detailing questions about the project or its direction

Comments

@tsalo
Copy link
Member

tsalo commented May 15, 2020

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.

@tsalo tsalo added the question issues detailing questions about the project or its direction label May 15, 2020
@jbteves
Copy link
Collaborator

jbteves commented May 15, 2020

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.

@jbteves
Copy link
Collaborator

jbteves commented May 15, 2020

🕯 a[0+]

@jbteves
Copy link
Collaborator

jbteves commented May 15, 2020

🔤 rc[1+]

@tsalo
Copy link
Member Author

tsalo commented May 15, 2020

Ugh so frustrating!!!! I'll change the vote-mojis then. Nvm your system's good.

@jbteves by the way you switched the emojis.

EDIT: I went ahead and changed the vote-mojis just to make the vote more obvious.

@emdupre
Copy link
Member

emdupre commented May 19, 2020

It seems that they can coexist according to semvar:

1.0.0-alpha < 1.0.0-alpha.1 < 1.0.0-alpha.beta < 1.0.0-beta < 1.0.0-beta.2 < 1.0.0-beta.11 < 1.0.0-rc.1 < 1.0.0.

Still, to reflect common usage I'd agree to adopt one or the other. My vote is for rc, but it's not a strong opinion.

@jbteves
Copy link
Collaborator

jbteves commented May 19, 2020

Oops, sorry, I missed that @tsalo

I'm fine with either, but do think we need to pick one.

@tsalo
Copy link
Member Author

tsalo commented May 19, 2020

@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?

@emdupre
Copy link
Member

emdupre commented May 19, 2020

How about we close the polls on Friday

Sounds reasonable to me !

@tsalo
Copy link
Member Author

tsalo commented Jul 14, 2020

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.

@tsalo tsalo closed this as completed Jul 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question issues detailing questions about the project or its direction
Projects
None yet
Development

No branches or pull requests

3 participants