-
-
Notifications
You must be signed in to change notification settings - Fork 272
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
Bincode 2 release #674
Comments
We will release bincode 2 when it's ready. All the maintainers have been very busy with non-OSS things this year, and we will not release untill all the issues tagged with |
It might make sense to have a label for bincode-2 blockers, as e.g. this ticket is labelled bincode-2 but doesn't block a bincode 2 release. That might help focus the energies of anyone keen to help this get released. |
How is bincode funded? I'm just a private individual so there's a limit to how much I can contribute but if enough individuals and companies really want v2 to be released, and if funds would actually be effective at making this happen I'm sure it could be organized. |
Currently bincode is not funded at all, the maintainers are contributing to this in their spare time |
Are there any guarantees surrounding the binary format between the current RC and the full release? At the moment I don't need a consistent format but I might require persistence of data that affects my decision between going with RC2 and v1. Thanks for your work! |
We are aiming to be binary compatible with bincode 1.3.3. If the current RC is binary compatible with 1.3.3, then the current RC will be compatible with the 2.0 release. It sounds like you might want to use 1.3.3 until 2.0 is released. |
Could I suggest pinning this issue or some other similar issue? The purpose would be to let users know Bincode 2 is coming, but it's not quite here yet. |
Good idea 👍 |
Its been a little bit since the last RC, what is left for bincode 2.0? Looking thru the issues i dont see any blockers so just curious what the status is. |
The big one is #517 If you'd like you contribute to the bincode 2.0 release, please have a look at the open issues: https://github.com/bincode-org/bincode/issues?q=is%3Aopen+is%3Aissue+label%3Abincode-2 |
I've been using bincode 2 RCs since the beginning of 2022. At that point my application was early in development and I thought it bincode 2 would release in the near future.
Are you planing to release bincode 2 this year? Otherwise I'm thinking about breaking binary compatibility and switching to a different framework. (As far as I can tell, RC2 -> RC3 already broke binary compatibility in a minor way. Although there is nothing in the release notes that would explain it.)
The text was updated successfully, but these errors were encountered: