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

Bump version from 0.5.3 to 0.6.0. #3420

Merged
merged 1 commit into from
Dec 1, 2018

Conversation

robertnishihara
Copy link
Collaborator

@robertnishihara robertnishihara commented Nov 27, 2018

No description provided.

@ericl
Copy link
Contributor

ericl commented Nov 27, 2018

In the future, should we always be on the "next" version? It's often confusing when you have 0.5.3 but it's actually 0.6.0-preview or something.

@atumanov
Copy link
Contributor

yeah, we could use 0.6.0-alpha,0.6.0-rc, 0.6.0

@robertnishihara
Copy link
Collaborator Author

@ericl, that makes sense, but right after we release 0.6.0, we don't necessarily know if the next release will be 0.6.1 or 0.7.0, so it's not clear if it should be 0.6.1a or 0.7.0a? How would you handle this? Just default to 0.7.0a?

@ericl
Copy link
Contributor

ericl commented Nov 27, 2018 via email

@AmplabJenkins
Copy link

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/9633/
Test FAILed.

@ericl ericl merged commit 0603e0b into ray-project:master Dec 1, 2018
@robertnishihara robertnishihara deleted the bumpversion branch December 1, 2018 19:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants