RLS: 1.2.1

[simonjayhawkins]

Tracking issue for the 1.2.1 release.

https://github.com/pandas-dev/pandas/milestone/81

Currently scheduled for January 18, 2021 (date flexible on severity of regressions)

List of open regressions: https://github.com/pandas-dev/pandas/issues?q=is%3Aopen+is%3Aissue+label%3ARegression

[simonjayhawkins]

current status: 8 open regressions milestoned 1.2.1, 2 with open PRs

https://github.com/pandas-dev/pandas/issues?q=is%3Aopen+is%3Aissue+label%3ARegression+milestone%3A1.2.1

(#38752 is a actually a regression in 1.1 but is milestoned 1.2.1)

[simonjayhawkins]

status update...

a week away from scheduled release. 9 open regressions milestoned 1.2.1, 1 with open PR #38980

https://github.com/pandas-dev/pandas/issues?q=is%3Aopen+is%3Aissue+label%3ARegression+milestone%3A1.2.1

#38969 is effectively a duplicate of #38947

#38851 maybe tricky to fix so maybe best to revert cleanup for 1.2.1. #38851 (comment)

#38946 is maybe not a priority so could remove from milestone #38946 (comment)

#38752 is a actually a regression in 1.1 but is milestoned 1.2.1

[jreback]

ok, can certainly try on these. but let's just do a time release. whatever we have is fine.

[simonjayhawkins]

ok, can certainly try on these. but let's just do a time release. whatever we have is fine.

yep, certainly on the patch releases (except the final in the series) a calendar based release schedule is fine.

[simonjayhawkins]

we've got the blocker label on #38787, should maybe discuss this on this week's dev call. cc @jorisvandenbossche @mroeschke

[simonjayhawkins]

although need not block, can revert backport, tag release, and re-apply backport if not resolved.

[jorisvandenbossche]

we've got the blocker label on #38787, should maybe discuss this on this week's dev call.

Yes, that would be a good topic to discuss (although don't know if Matt will be there). But I will try to look again at the issue and post my thoughts there.

[mroeschke]

I believe I can make the dev call this Wednesday to discuss #38787

[simonjayhawkins]

in the dev meeting notes for the release we have

Maybe revert plotting PR

@jorisvandenbossche I believe you suggested this.

I think that we should not yet revert until have investigated the issues further. 1.2.2 is scheduled for February 07, 2021 (3 weeks)

current status:

https://github.com/pandas-dev/pandas/issues?q=is%3Aopen+is%3Aissue+label%3ARegression+milestone%3A1.2.1

9 open regressions milestoned 1.2.1

5 linked to the visualization issue #39126, #38969, #38947, #38865 and #38736

#39184 requires further discussion/agreement on preferred course of action

#39115 and #39168 have open PRs

#38946 is not a priority for 1.2.1

[simonjayhawkins]

I think that we should not yet revert until have investigated the issues further. 1.2.2 is scheduled for February 07, 2021 (3 weeks)

from my limited understanding of the changes in that PR, I'm leaning towards the revert option.

If we do revert (for 1.2.1), should also have tests to prevent future regression. I'll open a PR for the revert, just in case, but won't be adding regression tests, so would need to leave the issues open with a 'needs tests' label.

[jorisvandenbossche]

I think that would be OK to just do the revert now, and add tests in follow-up PRs.