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

make 5.12.2 release #1358

Closed
alifeee opened this issue Dec 3, 2023 · 5 comments
Closed

make 5.12.2 release #1358

alifeee opened this issue Dec 3, 2023 · 5 comments
Assignees
Milestone

Comments

@alifeee
Copy link
Collaborator

alifeee commented Dec 3, 2023

Changes

@alifeee alifeee added this to the 5.12.2 milestone Dec 3, 2023
@lavigne958
Copy link
Collaborator

You take this one ? I take #1359 ?

Should we wait may be after 5.12.2 so users get the update etc we make sure we don't have regressions and then we release 6.0.0 , something like 2 weeks should cover us from any major issue I suppose?

@alifeee
Copy link
Collaborator Author

alifeee commented Dec 4, 2023

You take this one ? I take #1359 ?

Sure, sounds good :) will do #1359 as soon as #1362 is merged 👍

Should we wait may be after 5.12.2 so users get the update etc we make sure we don't have regressions and then we release 6.0.0 , something like 2 weeks should cover us from any major issue I suppose?

I think it doesn't matter because if there is an issue with 5.12.2, it will be an issue with the new get_records code, and

  • get_records is not a common method (I have no evidence for this other than there were not many issues about it being quite broken)
  • if we need to make a patch (e.g., 5.12.3) we can just make a branch based off of the 5.12.2 branch, and merge the fix into v6 (via master)

So we do not have to wait to make the 6.0.0 release

@alifeee
Copy link
Collaborator Author

alifeee commented Dec 4, 2023

@lavigne958 I think we should do the 6.0.0 release either in the next week or after Christmas, so we have time either way to fix issues. We should have a video call about 6.0.0 :)

@lavigne958
Copy link
Collaborator

agreed, I'll contact you to arrange the call, next week should be good.

@alifeee
Copy link
Collaborator Author

alifeee commented Dec 4, 2023

@alifeee alifeee closed this as completed Dec 4, 2023
@alifeee alifeee self-assigned this Dec 4, 2023
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