RLS: 0.24.x

[jreback]

Tracking issue for 0.24.1

[jreback]

@pandas-dev/pandas-core so it is very important to tag before you merge to a backport branch, otherwise the auto-backport-bot won't be triggered, e.g. we want to see something like #24951. Please make sure that these pass and then merge them (or you will need to manually fixup / merge to the backport branch).

[jorisvandenbossche]

I created the branch, so from now on, if you label a PR with 0.24.1 before merging, a backport PR will be created automatically if possible (and if not possible, a label will be added).

[jreback]

@jorisvandenbossche great thanks

[jorisvandenbossche]

And since Jeff and I already had some discussion about it :)

IMO, we should not be backporting too much, but limit ourselves to regressions and important bug fixes.

Backporting any tiny doc fix / bug fix is simply a) more work, and b) gives a higher risk of also breaking something unneeded.

[TomAugspurger]

Thought on doing a 0.24.1 soonish? Tracking a few regressions

• df.to_dict('records') broken when 255+ columns present #24939
• Index.intersection changed behavior to sort by default in pandas 0.24 #24959

I'd like to include #24964 as well (probably not a regression in 0.24, but I think important to have working, since that's hurting our import times).

any others?

[jreback]

we need to wait a few weeks - not worth it to do for these minor things

[TomAugspurger]

FYI releases are fairly cheap to do these days.

…

________________________________ From: Jeff Reback <notifications@github.com> Sent: Sunday, January 27, 2019 16:39 To: pandas-dev/pandas Cc: Tom Augspurger; Team mention Subject: Re: [pandas-dev/pandas] RLS: 0.24.1 (#24949) we need to wait a few weeks - not worth it to do for these minor things — You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub<#24949 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABQHItJgmvDciEWKS6uB8hb51s4-LvgYks5vHiqqgaJpZM4aUMuQ>.

[h-vetinari]

+0.5 for a fast release to fix the regressions before they got much chance to be relied on.

[jorisvandenbossche]

+1 on doing quick releases with regression fixes, if it is not a lot of work.
Certainly for the intersection sort behaviour it would be good to do this as fast as possible