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

Release bincode 0.7 #148

Closed
dtolnay opened this issue Apr 8, 2017 · 5 comments
Closed

Release bincode 0.7 #148

dtolnay opened this issue Apr 8, 2017 · 5 comments

Comments

@dtolnay
Copy link
Collaborator

@dtolnay dtolnay commented Apr 8, 2017

Serde 1.0 is happening in the next 6 weeks or so. Until then how about publishing bincode 0.7 with serde 0.9 support, then doing 1.0 along with us?

@TyOverby
Copy link
Collaborator

@TyOverby TyOverby commented Apr 8, 2017

Sounds good!

@TyOverby
Copy link
Collaborator

@TyOverby TyOverby commented Apr 8, 2017

I assume that you meant bincode 1.0.0-alpha7?

Also, are you publishing alpha versions of serde on crates.io?

@dtolnay
Copy link
Collaborator Author

@dtolnay dtolnay commented Apr 8, 2017

Nope, I meant bincode 0.7.0 with support for serde 0.9. I am not publishing alpha versions.

@TyOverby
Copy link
Collaborator

@TyOverby TyOverby commented Apr 8, 2017

Ah ok. I just published 0.7.0.

I am not publishing alpha versions.

Should I target your github branch for now then?

@dtolnay
Copy link
Collaborator Author

@dtolnay dtolnay commented Apr 8, 2017

Publishing alpha versions is a bad idea in general because of rust-lang/cargo#2222 - see #128 (comment). I will publish release candidate versions (rc1, rc2 etc) when I am ready. I would recommend that you maintain a branch that targets serde's "1.0" branch, not publish anything to crates.io until there is a serde release candidate, and yank your existing alpha versions to push people to use bincode 0.7.

@dtolnay dtolnay closed this Apr 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.