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

Revert #512 and #508 #663

Merged
merged 4 commits into from
Jan 23, 2025
Merged

Revert #512 and #508 #663

merged 4 commits into from
Jan 23, 2025

Conversation

jsdw
Copy link
Contributor

@jsdw jsdw commented Dec 2, 2024

Quick attempt to revert these PRs mentioned in #662 (comment)

@jsdw
Copy link
Contributor Author

jsdw commented Dec 2, 2024

For my own benefit: I realised just now that the recent releases prior to 3.7.0 all came off the 3.6.x branch, which had the above PRs reverted also. I totally missed this branch when doing the latest release, assuming everything was released off master!

I think it would be good to get master back to a sane point. Maybe we should not try to merge this PR at all (which we would do just to get 3.7.1 out, and then want to undo anyways for 4) and instead just release 4.0.0 directly now that we've yanked 3.7.0 and deal with the fallout of this major bump. Does that sound fair?

@serban300
Copy link
Contributor

For my own benefit: I realised just now that the recent releases prior to 3.7.0 all came off the 3.6.x branch, which had the above PRs reverted also. I totally missed this branch when doing the latest release, assuming everything was released off master!

I think it would be good to get master back to a sane point. Maybe we should not try to merge this PR at all (which we would do just to get 3.7.1 out, and then want to undo anyways for 4) and instead just release 4.0.0 directly now that we've yanked 3.7.0 and deal with the fallout of this major bump. Does that sound fair?

@jsdw what you're saying makes sense, but personally I would need a 3.7.1 release soon-ish in order to access the functionality introduced in #616 and I think we would have to wait quite a while for a 4.0 release

So could we have a v3.7.x branch for now that would include this PR, and then release 3.7.1 from it ? I can do it if you want. Just please let me know how you prefer

@bkchr
Copy link
Member

bkchr commented Jan 22, 2025

Let's merge this pr and add it to the 4.0 milestone (so we can take care of it in the future :P)

@serban300
Copy link
Contributor

Let's merge this pr and add it to the 4.0 milestone (so we can take care of it in the future :P)

Sounds good to me. We just need to fix the failing test (Rust CI/CD / tests (pull_request)) .@jsdw I can do it if you want. However you prefer.

@serban300 serban300 merged commit 96269d4 into master Jan 23, 2025
17 checks passed
This was referenced Jan 23, 2025
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

Successfully merging this pull request may close these issues.

3 participants