-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
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
RLS: 2.0.1 #52383
Comments
Is this still planned for May or are the issues fixed more urgent? |
We talked about this in the dev meeting and agreed releasing in around 2 weeks makes sense, thoughts @datapythonista? Does this fit with your schedule? |
Yes, sounds great. I won't have much time for anything this week and the next, but I'll be back to normal after, so the 24 could be a good day to release. Also, a lot of the release has been automated and I think the release process documentation is quite clear and detailed, so I think it should be easy for someone else to take care of it if needed. But as said, I can release on the 24, or also after the meeting of the 26 which I should be able to attend again (I finished the training I was giving in that time slot). |
nice - yeah 24th sounds good! |
Just as a heads up: NumPy dev build is failing (#52853). Shouldn't block the release |
All green except the numpy dev problem. Cutting the release now, moving all issues in the 2.0.1 to 2.0.2, I'll be probably tagging today, and leave things building to release tomorrow. |
I created the tag, the GitHub release and opened the conda-forge PR. I'll continue the release tomorrow (Europe timezone) when all the packages are created. |
Couple of ARM packages in conda-forge are still being generated, but other than that the release is complete and has already been announced. I opened #52892 for the 2.0.2 release. I think tagging in the evening before the release is more convenient, planning to do that again for future releases. |
This is the tracker for the 2.0.1 release. I think we can have it in around one month, unless some problem in 2.0 requires an earlier release.
The text was updated successfully, but these errors were encountered: