RLS: 1.2.2

[simonjayhawkins]

Tracking issue for the 1.2.2 release.

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

Currently scheduled for February 07, 2021

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

[simonjayhawkins]

This is a calendar release scheduled for today.

there are some open PRs milestoned 1.2.2 https://github.com/pandas-dev/pandas/pulls?q=is%3Aopen+is%3Apr+milestone%3A1.2.2

some are close to being ready. Please comment if the release should block on any of these.

cc @jreback @jorisvandenbossche

[jreback]

will look soon

[simonjayhawkins]

no problem. I think all are ready be merged except #39615

[jreback]

yep ok with pushing that off if you would like to do the release. can move all issues to 1.2.3

[simonjayhawkins]

sure. won't move any issues till backports are complete and MacPython/pandas-wheels#126 is merged and green (currently failing on PR)

[rhshadrach]

@simonjayhawkins @jreback I've updated #39547 and it is ready on my end. It would be great if this could get into 1.2.2 but certainly okay if it waits till 1.2.3.

[simonjayhawkins]

pre-release checklist

• test wheel build status in advance of 1.2.2 release MacPython/pandas-wheels#125
• 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.2.2.html
• ci checks https://github.com/pandas-dev/pandas/commits/1.2.x
• no manual backports outstanding https://github.com/pandas-dev/pandas/pulls?q=is%3Apr+label%3A%22Still+Needs+Manual+Backport%22+is%3Aclosed
• no open issues/PRs (except this one) https://github.com/pandas-dev/pandas/milestone/82

current status:

5 open PRs. https://github.com/pandas-dev/pandas/pulls?q=is%3Aopen+is%3Apr+milestone%3A1.2.2

#39641 will be merged last

will open a PR shortly for the release date (and clear the empty list items which will create a conflict with #39547).

will also start moving the remaining issues off the milestone shortly, after MacPython/pandas-wheels#125 completes. (nightlies built ok, so 1.2.x should be the same)

[simonjayhawkins]

will also start moving the remaining issues off the milestone shortly, after MacPython/pandas-wheels#125 completes. (nightlies built ok, so 1.2.x should be the same)

green

[simonjayhawkins]

since azure is so slow, i'm thinking of cancelling some workflows. this may backfire if the last commit fails and it's not obvious which commit caused the failure.

I think that if we wait for them to complete, by the time we've done the pre-release checklist, we won't be releasing today.

I'm ok with doing release tomorrow though.

[simonjayhawkins]

one thing to note. to avoid uploading the docs we don't run Github actions on the commits to 1.2.x. Now that there are many other jobs run on Github actions we should revisit this and not just rely on the ci for the backport PR.

[jreback]

@simonjayhawkins all sounds good. do what you need to do. possibly enhance the release docs with tips like these at some point.

[simonjayhawkins]

will be patient and leave the release till tomorrow.

our release docs don't have anything about preparing for the release. for this reason I use the release tracking issue (i.e. this one) to document each step and progress.

for the Github actions issue, I should open a new issue and xref #38360. we may want to activate Github actions for pushes to 1.2.x and update .github\workflows\ci.yml which will currently upload docs on a push event...

    - name: Upload web
      run: rsync -az --delete --exclude='pandas-docs' --exclude='docs' --exclude='Pandas_Cheat_Sheet*' web/build/ docs@${{ secrets.server_ip }}:/usr/share/nginx/pandas
      if: github.event_name == 'push'