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.0.1 #31523

Closed
TomAugspurger opened this issue Jan 31, 2020 · 9 comments
Closed

RLS: 1.0.1 #31523

TomAugspurger opened this issue Jan 31, 2020 · 9 comments
Labels
Milestone

Comments

@TomAugspurger
Copy link
Contributor

TomAugspurger commented Jan 31, 2020

A decent number of regressions have been reported on 1.0.0. I think we should target 1.0.1 for sometime early next week. Perhaps on Tuesday, depending on how much progress we make on the regressions.

cc @pandas-dev/pandas-core.

make sure these are backported

@TomAugspurger TomAugspurger added this to the 1.0.1 milestone Jan 31, 2020
@jreback
Copy link
Contributor

jreback commented Feb 1, 2020

A decent number of regressions have been reported on 1.0.0. I think we should target 1.0.1 for sometime early next week. Perhaps on Tuesday, depending on how much progress we make on the regressions.

cc @pandas-dev/pandas-core.

sgtm going to review open things tomorrow

@TomAugspurger
Copy link
Contributor Author

How do things look for a release today? The 1.0.1 milestone has a handful of issues.

The others should have PRs that can be merged shortly.

@jorisvandenbossche
Copy link
Member

Personally, I would just release today with whatever is merged, the remaining tickets can be moved to the 1.0.2 milestone.

@jreback
Copy link
Contributor

jreback commented Feb 5, 2020

agree

having 1.02 in say 2 weeks should cover additional regressions

@jreback
Copy link
Contributor

jreback commented Feb 5, 2020

note that 2 PR are tagged with manual backport needed (link at top)

@jorisvandenbossche
Copy link
Member

Those are manually merged in the meantime (forgot to remove the label for those)

@TomAugspurger
Copy link
Contributor Author

I think #31677 and #31623 should wait for 1.0.2. #31623 seems especially tricky. I'll post a workaround on the issue.

If we're OK with that, we can go ahead with releasing 1.0.1 now. @jorisvandenbossche did you want to handle it, or should I?

@TomAugspurger
Copy link
Contributor Author

Joris let me know that I should start the release process. He'll pick it up when he's free in a couple hours.

@jorisvandenbossche
Copy link
Member

Wheels and sdist are uploaded to PyPI, conda-forge packages also built.

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

4 participants