-
Notifications
You must be signed in to change notification settings - Fork 71
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 to v0.26 #1161
Bump version to v0.26 #1161
Conversation
If we want to change the MSRV policy, we should discuss in a group, with @steveblackburn and @caizixian involved. From our previous discussion, we acknowledge that MMTk is a research project and may be aggressive with the technology we use. Our lab machine images are updated automatically, so our burden of maintenance is not high. We should also communicate with our collaborators and see if there are requirements for a less aggressive MSRV policy. |
I removed the changes about the MSRV policy in this PR. But I still suggest we adopt a less aggressive policy. We currently use N-1. But in practice, we are not aggressively moving the MSRV, as we know sticking to N-1 all the time would bring troubles, and that is not desirable. However, sticking to N-1 is a valid option according to our policy. Using N-4 or something similar would set a more clear expectation for our users and contributors. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
binding-refs |
This PR bumps the version to v0.26.