-
-
Notifications
You must be signed in to change notification settings - Fork 18.1k
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.2.0 #54902
Comments
@pandas-dev/pandas-core I'm thinking about cutting a release for the 2.2.0 RC next next Wednesday (the 6th of December). This sets us up nicely for an actual release on the 20 of December before Christmas/New Years. Any thoughts on this date? |
Seems reasonable to me |
I would prefer not to release directly before Christmas, rather first week of January. We need some more warnings for CoW as well, not sure if we can get all of them till December 6th |
There are a bunch of deprecations id like to get in for 2.2 as well |
I would be OK postponing, but It would be good to list in the OP what items people ideally want to get in before an RC |
I'm fine with a delay, looks like numpy is pushing back their 2.0 release anyways. Also, it'd be helpful if people edit the OP to list blockers or things they'd like to get in. |
I'd be fine with cutting the rc end of December if that's possible for you @lithomas1, no worries if not, otherwise first week of January? |
Sure, does anytime during the week of Dec 18-22 work for you? |
@natmokval if there's any deprecations you'd like to get in before 2.2, your input would be valued (including if this timeline looks good)! |
That should work for me, yes. And then cut the actual release 8th-12th of January? |
Sure, I'll updated the OP with the tentative timeline then. If anyone else has any concerns about the date, feel free to comment below. I'm pretty free from mid December to mid January, so am pretty flexible about moving the release date. |
Looking at my list of deprecations I decided I want many of them but none of them are blockers. |
@pandas-dev/pandas-core friendly reminder that I'm planning to release the RC tmrw. If anyone has anything they really like to get in before the RC, now would be the time to comment. |
#56346 is essentially the last piece of the "offset aliases overhaul" puzzle - I think the whatsnew note can be improved, but other than that it looks good OK to merge in time for the RC, with the understanding that the whatsnew note will be improved in time for the final 2.2 release? |
yes |
thanks - just going out for lunch but will merge in the next few hours if it's fine not a blocker anyway, don't feel like you need to wait for it |
there's some things I'm not sure about in there, so let's not rush things through - it can be deprecated as part of the 3.x cycle, no big deal So, feel free to release the RC, doesn't look like others have objections either 🚀 |
@pandas-dev/pandas-core Starting the RC release in ~10 minutes, please don't merge anything to main during this time. |
@pandas-dev/pandas-core All clear! |
@pandas-dev/pandas-core Starting the release now, please don't merge anything to 2.2.x anymore. |
Just a quick update on the release: The Windows builds just failed because of the difference in newlines on Windows ('\r\n') vs Unix('\n) for the test for the deprecationwarning for missing pyarrow. The fix shouldn't be too hard, so I'm still going to try to release today. |
release was announced. |
Thanks for another release @lithomas1. Do you want to create an issue to track the 3.0 release? I can do it myself, but probably worth adding when you expect to release it. |
Feel free to do so. I'm not too sure when it's possible to release it (I guess April/Mayish). |
Tentative schedule:
RC: 12/22/2023
Actual release: 1/10/2024
blockers
nice to have:
The text was updated successfully, but these errors were encountered: