-
-
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: 1.4.1 #45551
Comments
We have just over 20 bug fixes listed in the 1.5.0 release notes. (i.e. merged to main since the fork for the rc) Any objections/interest is looking to maybe backport those to 1.4.x for the 1.4.1 release? |
i suppose very targeted ones are ok though generally we don't do these |
@pandas-dev/pandas-core @pandas-dev/pandas-triage planning a calendar release for tomorrow, open issues will be moved to 1.4.2 later today 1.4.2 scheduled for March 05, 2022, i.e. 3 weeks from tomorrow. https://github.com/pandas-dev/pandas/milestone/94 |
all open issues have been moved. looking good to get started on the release in the morning (UK time). CI is taking some time lately and not fully green and the dev docs have not been updated since yesterday. wheels build check ok earlier today and will be checked again before release. The docs issue is now fixed #45690 (comment) so should be able to check the release notes before starting the release after the next commit to main and upload the release docs tomorrow. Checking the docs is also part of the release process after tagging locally anyway. |
release checklist for commit 47e3b40
|
starting release now
|
Tracking issue for the 1.4.1 release.
https://github.com/pandas-dev/pandas/milestone/93
Currently scheduled for February 12, 2022
This is 3 weeks from today assuming a release schedule of 3-3-4-5-6 weeks for 1.4.1 through 1.4.5, but date would be flexible on severity of any reported regressions.
List of open regressions: https://github.com/pandas-dev/pandas/issues?q=is%3Aopen+is%3Aissue+label%3ARegression
The text was updated successfully, but these errors were encountered: