-
Notifications
You must be signed in to change notification settings - Fork 4.3k
Set first release version and fix gulp release pipeline #328
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
Conversation
Starting version is fine. As for the semantic versioning I think more common format is:
I like first better. What do you think? |
Current coverage is
|
I think I prefer the second option
|
I didn't want to add hyphen, because kubernetes addons have a requirement to not have it in the version (yeah, that's sad). So how about going with just |
Yeah, that's disappointing. I'd go with clean PS. Does |
It does not, but semver needs a dash between |
Oh yeah. I see now. Due to our proxy I could not open semver page correctly... |
The best version would be |
Fine by me |
Cool
|
I propose that we start with version 0.1 and use semantic versioning.
Updated. PTAL. |
LGTM |
Set first release version and fix gulp release pipeline
I propose that we start with version 0.1 and use semantic versioning.