RLS: 1.3

[simonjayhawkins]

Tracking issue for the 1.3 release.

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

Currently scheduled for May 31, 2021

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

[simonjayhawkins]

Currently scheduled for May 31, 2021

so we should be releasing the 1.3.0rc0 shortly (late next week or week after?), with the release of 1.3.0 a couple of weeks later

if we do 1.3.0 in mid/late June then from https://numpy.org/neps/nep-0029-deprecation_policy.html

On Dec 26, 2021 drop support for Python 3.7 (initially released on Jun 27, 2018)

The next release can be scheduled for 6 months, and we can drop 3.7 support in the next release.

v1.2.0 was released on Dec 26, 2020, so these dates seem consistent.

when v1.3.0rc0 is released we branch straight away so that we can continue to work on master during the rc period (this is how it was done for v1.2.0rc0)

so immediately after v1.3.0rc0 we can drop support for python 3.7 on master.

---

once v1.3.0rc0 is released, we will only backport regression fixes, maybe some bugfixes, maybe extra work on new enhancements and maybe also changes to experimental features.

---

when v1.3.0rc0 is released, we also tag master (v2.0.0.dev0 and add a whatsnew)

so immediately after v1.3.0rc0 we can start deprecating the deprecations introduced in 1.x (may need discussion regarding deprecations introduced late in the 1.x series)

[jreback]

can u open an issue about dropping 3.7

[simonjayhawkins]

about doing it, or discuss whether to do it?

[jreback]

yeah to do it

[jreback]

@simonjayhawkins lets do the RC soon - waiting for the remaining pr labeled for 1.3 is not worth it

[simonjayhawkins]

hmm, we should get #39908 in. I think definitely worth it.

v1.2.0 was released on Dec 26, 2020 and the next release would ideally be after Dec 26, 2021 so we can drop Python 3.7

so a release around Jun 26, 2021, with a rc 2 weeks before around 12th gives us at least a few days to sort out the loose ends.

anytime next week would be consistent with these dates.

(and get 1.2.5 done first)

[simonjayhawkins]

once v1.3.0rc0 is released, we will only backport regression fixes, maybe some bugfixes, maybe extra work on new enhancements and maybe also changes to experimental features.

I am planning to continue with some PyArrow string array changes after the rc (add arithimetic ops, min and max, more documentation and carry on with some perf improvements of the str accessor methods)

this list of open PRs milestone 1.3 https://github.com/pandas-dev/pandas/pulls?q=is%3Aopen+is%3Apr+milestone%3A1.3 contains some doc changes, which can also be done during the rc period.

#41718 is now ready and the last of the deprecations in #41485 with just a doc update outstanding #41485 (comment) that can be done during the rc.

#41654, #41586, #39908 and #35417 have behavioral changes to core functionality that if not merged before the rc. should probably wait to the next release.

We should be on course to release 1.3.0rc0 this week assuming we can finish up the 4 PRs mentioned above.

[lithomas1]

@simonjayhawkins Will there be a 1.4 release? Looks like there is a milestone created on Github for it.

[jreback]

i created 1.4; it's possible we make this 2.0 at some point - not determined yet

[simonjayhawkins]

rc pre-release checklist

• ✅ MacPython.pandas nightly wheels built ok - https://dev.azure.com/pandas-dev/pandas-wheels/_build?definitionId=3&_a=summary
• ⬜ wheels building - final check
• ⬜ release readiness passing https://github.com/simonjayhawkins/pandas-release/actions?query=workflow%3A%22Tag+Release%22
• ✅ release notes checked https://pandas.pydata.org/pandas-docs/dev/whatsnew/v1.3.0.html
• ✅ ci checks https://github.com/pandas-dev/pandas/commits/master
• ❌ no open PRs milestoned 1.3 https://github.com/pandas-dev/pandas/pulls?q=is%3Aopen+is%3Apr+milestone%3A1.3
• ⬜ no open issues milestoned 1.3 that are not suitable backport candidates https://github.com/pandas-dev/pandas/issues?q=is%3Aopen+is%3Aissue+milestone%3A1.3
• ❌ no open blockers https://github.com/pandas-dev/pandas/milestone/80

I think #41888 is the only open PR that is now outstanding, the others can be moved of the milestone or merged during rc

[simonjayhawkins]

• ❌ no open PRs milestoned 1.3 https://github.com/pandas-dev/pandas/pulls?q=is%3Aopen+is%3Apr+milestone%3A1.3
• ⬜ no open issues milestoned 1.3 that are not suitable backport candidates https://github.com/pandas-dev/pandas/issues?q=is%3Aopen+is%3Aissue+milestone%3A1.3
• ❌ no open blockers https://github.com/pandas-dev/pandas/milestone/80

will combine these three into checking for "Blocker for rc" label, so use that label for anything that should be done for the rc otherwise will release.

[simonjayhawkins]

rc pre-release checklist

• ✅ MacPython.pandas nightly wheels built ok - https://dev.azure.com/pandas-dev/pandas-wheels/_build?definitionId=3&_a=summary
• ⬜ wheels building - final check
• ⬜ release readiness passing https://github.com/simonjayhawkins/pandas-release/actions?query=workflow%3A%22Tag+Release%22
• ⬜ release notes checked https://pandas.pydata.org/pandas-docs/dev/whatsnew/v1.3.0.html
• ❌ ci checks https://github.com/pandas-dev/pandas/commits/master
• ❌ no open issues labelled blockers for rc https://github.com/pandas-dev/pandas/issues?q=is%3Aopen+is%3Aissue+label%3A%22Blocker+for+rc%22+milestone%3A1.3
• ✅ no open PRs labelled blockers for rc https://github.com/pandas-dev/pandas/pulls?q=is%3Aopen+is%3Apr+milestone%3A1.3+label%3A%22Blocker+for+rc%22

[jreback]

let's move all issues off of 1.3 except for the specifically mentioned ones. If there are no PRs then we are not waiting.