Skip to content
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.

Publish another beta? #642

Closed
callumlocke opened this issue Jan 28, 2015 · 4 comments
Closed

Publish another beta? #642

callumlocke opened this issue Jan 28, 2015 · 4 comments

Comments

@callumlocke
Copy link

Would it be possible to do another beta release, as 2.0.0-beta.2? There's been some important fixes since then

@am11
Copy link
Contributor

am11 commented Jan 29, 2015

No. The next version would be 2.0.0-stable.

@am11 am11 closed this as completed Jan 29, 2015
@callumlocke
Copy link
Author

you know semver explicitly allows multiple beta versions? The first one should be x.x.x-beta, then others (if necessary) are x.x.x-beta.2, etc – see rule 11 on semver.org

(or if you're saying you just don't want to publish an updated beta, that's your call, but why?)

@am11
Copy link
Contributor

am11 commented Jan 29, 2015

Because 2.0.0 stable is ready and there is no point for another beta and redoing the binaries, which we are not able to get for the ready version in first place.
We are waiting for Linux binaries for which we are waiting for some GCC build system expert (black-belt kinda person) to steer our boat in right direction and fix the compatibility issues with old CentOS: #602 so we don't have another situation like #517.

@callumlocke
Copy link
Author

ah I see, thanks for the explanation

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants