-
Notifications
You must be signed in to change notification settings - Fork 119
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
Anything to do before making a new breaking release? #51
Comments
I think we should consider whether this is the right time to remove deprecated stuff. The things I know of are:
Otherwise I think this would be a really nice time to do a new release, and I cannot think of any important improvements right now. I can think of a few non-important ones improvements, that I might be interested in exploring at some point, but even then I do not think any of them would break backwards compatibility.
I do not have any current needs for any of them though, so I think it is unlikely that I will get around to exploring them in the near future (or ever). |
@fitzgen Are you still planning on doing a release soon? |
Yeah, sorry been a bit busy and travelling a bunch. |
We have had a bunch of great work committed to master that I'd like to publish, and some of it is breaking (the reversal of bump direction, for example). Because it is breaking, I'd like to double check that we aren't missing any breaking changes that we can coalesce into a single release, rather than eventually doing multiple breaking releases.
@TethysSvensson, anything else on your radar? Anything else needed for your flatbuffers effort?
cc @vorner
TODO
Commits since the last release
alloc_layout_slow
#45 from fitzgen/alloc-layout-slow-alignmentalloc_layout_slow
dbg!
from debugging #40 from fitzgen/remove-dbgdbg!
from debuggingThe text was updated successfully, but these errors were encountered: