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: 0.25.2 #28110

Closed
TomAugspurger opened this issue Aug 23, 2019 · 16 comments
Closed

RLS: 0.25.2 #28110

TomAugspurger opened this issue Aug 23, 2019 · 16 comments
Labels
Milestone

Comments

@TomAugspurger
Copy link
Contributor

cc @pandas-dev/pandas-core

Python 3.8 is due on October 21, which will likely beat 1.0.

We should release a 0.25.2 around then that's just 0.25.1 + 3.8 compatibility and regressions from 0.24.x.

@TomAugspurger TomAugspurger added this to the 0.25.2 milestone Aug 23, 2019
@jorisvandenbossche
Copy link
Member

I don't think we need to wait until then? (the sooner it is already out, the less people will have issues when updating to 3.8)
So I would just continue backporting regressions (but we can be conservative in backporting, no need to backport normal bug fixes), and we can always see when we have accumulated some fixes.

@TomAugspurger
Copy link
Contributor Author

Yeah, that's just the deadline.

We'll also need to handle building 3.8 binaries after the release. I think that should be doable (just bump the build number on conda-forge when they're ready, and upload only the 3.8 wheels from multibuild).

@stonebig
Copy link
Contributor

stonebig commented Aug 26, 2019

shouldn't a bug fix be released with Python-3.8.0rc1 (sept 30th), so that users trying Python-3.8.0rc can look for un-solved bugs only ?

@TomAugspurger
Copy link
Contributor Author

The earlier the better probably. We need to get things running on our CI first though.

@TomAugspurger
Copy link
Contributor Author

FYI, @jbrockmendel and I may try to knock out a release this week while we're in town together (likely on Thursday). Ideally we'll be able to get a bit of CI coverage on 3.8 before then.

@jreback
Copy link
Contributor

jreback commented Oct 1, 2019

is conda-forge any better at 3.8 now?

@TomAugspurger
Copy link
Contributor Author

TomAugspurger commented Oct 1, 2019 via email

@TomAugspurger
Copy link
Contributor Author

3.8 is out now. @jbrockmendel are you free to do a release tomorrow?

I think the remaining prep work is just to clean up the v0.25.2.rst whatsnew (spell check, add a release date, general cleanup) on master and backport

@TomAugspurger
Copy link
Contributor Author

The 0.25.x branch should be almost ready.

We have

then I think we're ready.

I can't actually do the release this time around. My main laptop is being serviced, and I don't think the machine I'm on can physically run docker. Hopefully @jbrockmendel is able to today (I'll be around to assist). @jbrockmendel can you confirm that you're jbrockmendel on PyPI? @jreback can you add him as a maintainer on PyPI when he's done so?

@TomAugspurger
Copy link
Contributor Author

3.8 Binaries

In MacPython/pandas-wheels#64, we're testing our wheel infrastructure on 0.25.x with 3.8. I have two questions

  1. What version of NumPy can / should those be built against? @rgommers @matthew-brett do you have recommendations? I assumed I needed 1.18.0.dev0, since that's the first NumPy to be compatible with Python 3.8. Is building wheels to be published on PyPI against a dev version of NumPy a bad idea? We can wait to build / upload 3.8 wheels until later.
  2. @cgohlke are you set up for building 3.8 wheels? What version of NumPy will you build those against?

Conda-forge is working on 3.8 packages. Those will likely take a bit longer.

@rgommers
Copy link
Contributor

Is building wheels to be published on PyPI against a dev version of NumPy a bad idea? We can wait to build / upload 3.8 wheels until later.

Yes I think that's not the best idea. @charris is planning to release a Python 3.8 compatible NumPy 1.17.3 shortly, so that's a much better target. Wheels built against 1.18.0.dev0 likely won't work with 1.17.3.

@TomAugspurger
Copy link
Contributor Author

Ah, good to know about the 1.17.3 release. I'll keep my eye on numpy/numpy#14698. We can hold off on releasing 0.25.2 until those are ready.

@jreback
Copy link
Contributor

jreback commented Oct 15, 2019

@jbrockmendel added to pypi

@TomAugspurger
Copy link
Contributor Author

OK the 0.25.x branch should be good to go. Will coordinate with @jbrockmendel on releasing.

Personally, I'm OK with waiting on NumPy 1.17.3 wheels. We could release 0.25.2 at any time and rebuild wheels for 3.8 when NumPy is ready. But if NumPy is close (next day or two) then it's a tad less work to do it all at once.

@manselmi
Copy link

FYI NumPy 1.17.3 wheels (including wheels for Python 3.8) are now available on PyPI.

@TomAugspurger
Copy link
Contributor Author

Wheels, and conda-forge packages are up (will need to follow up on 3.8 conda packages on conda-forge). Docs are up, sent out the announcements.

Something is up with the pdf build: pandas-dev/pandas-release#18 Will get to that eventually.

Thanks for running the release @jbrockmendel.

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

6 participants