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

Draft a release explaining the breaking changes & lay roadmap for 1.0 #91

Open
chanced opened this issue Oct 21, 2024 · 4 comments
Open

Comments

@chanced
Copy link
Owner

chanced commented Oct 21, 2024

Draft a release for 0.7

Edit: 0.7, not 8

@chanced
Copy link
Owner Author

chanced commented Oct 21, 2024

I haven't marked a release since 0.4. I should probably go back and do 0.5, 0.6, 0.7 as well.

@asmello
Copy link
Collaborator

asmello commented Oct 21, 2024

Somewhat related, I just noticed core::error::Error was stabilised in 1.81, so we should track removing the Error implementations from the std feature flag next time we bump the minimum Rust version.

@chanced
Copy link
Owner Author

chanced commented Oct 21, 2024

Yea, I was happy to see that one land. I wasn't sure what the expectation is in regards to min required rust. Do people typically keep up to date? Surely its not as bad as the land of Java (just checked, seems 17 surpassed 11 in 2024).

@asmello
Copy link
Collaborator

asmello commented Oct 22, 2024

It really varies a lot. I think ~6mo is probably reasonable lag before bumping the minimum version. Rust is pretty good about backwards compatibility and stability so there's no real reason for people to not upgrade often.

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

No branches or pull requests

2 participants