Skip to content
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: 1.2.5 #40917

Closed
simonjayhawkins opened this issue Apr 13, 2021 · 20 comments
Closed

RLS: 1.2.5 #40917

simonjayhawkins opened this issue Apr 13, 2021 · 20 comments
Labels
Milestone

Comments

@simonjayhawkins
Copy link
Member

Tracking issue for the 1.2.5 release.

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

Currently scheduled for May 10, 2021

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

@simonjayhawkins simonjayhawkins added this to the 1.2.5 milestone Apr 13, 2021
@xmatthias
Copy link

Any chance of having #40505 backported to 1.2.5?

it's fixing a regression that ocured between 1.1.5 and 1.2.0, so i think this should be considered for a backport.

@jreback
Copy link
Contributor

jreback commented Apr 21, 2021

@xmatthias no that would be a too subtle change for a patch release

@xmatthias
Copy link

xmatthias commented Apr 21, 2021

@jreback considering that it was an undocumented regression / behaviour change between 1.1.5 and 1.2.0, i tend to disagree, as a patch release is in my understanding something that will address regressions.

@phofl
Copy link
Member

phofl commented May 24, 2021

This does fix a regression yes, but it also changes the behavior in certain cases, so agree with @jreback here, to subtle to include in 1.2.5

@simonjayhawkins
Copy link
Member Author

tl;dr lmk if any blockers @pandas-dev/pandas-core @pandas-dev/pandas-triage


it's probably be easier if we release 1.2.5 (if we are going to have another patch release in 1.2.x) before 1.3.0rc0.

so should probably think about releasing early next week.

lmk if any blockers, if we do another release on 1.2.x, I expect this to be the last in the series, so unlike the other patch releases that were calendar based, we want to make sure we include anything that should be included so that we don't need to do another.

We only have 2 patches, 1 of which was not trivial, so we could also decide not to do another patch release on 1.2.x

There's 1 open PR for a regression but's that's for an undocumented usage so could decide not to fix.

@jreback
Copy link
Contributor

jreback commented May 26, 2021

prob ok to release as we have right now

@simonjayhawkins
Copy link
Member Author

we have a few outstanding issues but no PRs to fix. https://github.com/pandas-dev/pandas/milestone/85 except #41806

so could maybe do release after that one.

I've not yet got round to look at #41797 in detail, but looking at the diff of the PR that caused the regression https://github.com/pandas-dev/pandas/pull/37355/files, any fix is probably backportable.

also not sure if all the regressions in 1.2.x have been milestoned. could take the time to go back over the open issues.

This is hopefully the last in the 1.2.x series, so any delay to fix the outstanding issues maybe worthwhile.

Ideally want to release 1.2.5 before 1.3.0rc but can workaround if not.

@jreback
Copy link
Contributor

jreback commented Jun 4, 2021

the 1.2.x should be orthogonal to the 1.3.x i think

but yeah let's just release 1.2.5 when ready

@simonjayhawkins
Copy link
Member Author

the 1.2.x should be orthogonal to the 1.3.x i think

if we do it after, we need to backport anything from master to both 1.2.x and 1.3.x. nbd.

@jreback
Copy link
Contributor

jreback commented Jun 4, 2021

well only if we are actually patching 1.2,x (which at this point should be very very minimal)

@simonjayhawkins
Copy link
Member Author

very very minimal

sure. and autobackporting to 1.3.x from master after the fork at 1.3.0.rc0 should just work in more cases until the branches are significantly diverged.

if we can do 1.2.5 before 1.3.0.rc0 great, but we don't need to block 1.3.0.rc0 on 1.2.5

@jorisvandenbossche
Copy link
Member

Note that #41711 might have given a performance regression, which might be best to check first since that's backported to the 1.2.x branch.

@simonjayhawkins
Copy link
Member Author

Thanks @jorisvandenbossche I think we were ready to go with 1.2.5 last week and then #41797 (and #41778 but that is now fixed) was reported and i've not got round to look at it and no PRs have been open for this, so 1.2.5 has been delayed anyway.

@jorisvandenbossche
Copy link
Member

I have a small PR for fixing the performance regression: #41920, so that should address this issue for 1.2.5.

@simonjayhawkins
Copy link
Member Author

@pandas-dev/pandas-core I'm going to try and replicate the issue with the release readiness scripts locally https://github.com/simonjayhawkins/pandas-release/actions?query=workflow%3A%22Tag+Release%22 and then look at #41797 after if no-one else gets a chance before. So could maybe release 1.2.5 in the next couple of days?

@simonjayhawkins
Copy link
Member Author

simonjayhawkins commented Jun 17, 2021

I'm going to try and replicate the issue with the release readiness scripts locally https://github.com/simonjayhawkins/pandas-release/actions?query=workflow%3A%22Tag+Release%22

couldn't isolate which dependency change actually broke the github workflow but changing from conda build to conda-build fixed.

conda build gives a "[y/N]" prompt and does nothing.

@simonjayhawkins
Copy link
Member Author

all pre-release checks passed. closing down milestone and starting release shortly.

@simonjayhawkins
Copy link
Member Author

simonjayhawkins commented Jun 22, 2021

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants