Release manager needed for pandas 0.24.3

[datapythonista]

The next version of pandas will be 0.25.2, but we'll release another version of 0.24, the 0.24.3 since pip install pandas may fail in Python 2. The pandas 0.24 series is the last compatible with Python 2, but numpy released a new Python 2 compatible version, that can be automatically installed with pip install pandas, and that is not compatible with pandas 0.24.

The proposed solution is to release a new version 0.24.3, with the only change respect to 0.24.2 that requires numpy < 1.17.

See the original issue here: pandas-dev/pandas#27435

Making the change to setup.py is trivial, but releasing a new pandas version not as much (never did it myself). Most of the work will be in understanding the process, and also on building packages (for pip and for conda). Couple of the steps will require the right permissions (access to the server where we have the documentation, and commit rights on the pandas git repo, but someone with those permissions can take care of those steps.

Those are the notes from the meeting where this was discussed:

• pip install pandas works when there’s a binary available.
• pip install --no-binary=pandas pandas numpy==1.16 fails
• pip install numpy && pip install --no-binary=pandas pandas works (if you have a compiler)
• We need a PR to update numpy dependency environment marker for just py 27. Backport to 0.24.x
• Then one of us has to tag 0.24.3 we do the sdsit to github
• Someone builds binaries on CF(?) wheels.
• One of use uploads binaries and sdist to pypi.

[TomAugspurger]

Most of this is semi-automated in https://github.com/pandas-dev/pandas-release (using docker for the local stuff, and making pull requests to GitHub).

[Aya-S]

How realistic do you think is it to have someone who is a noob attempt this?

[datapythonista]

How realistic do you think is it to have someone who is a noob attempt this?

If you're motivated to do it, you should totally do it. It'll require a bit of time to understand things (like, building coda packages...), but there is nothing challenging that you can end up saying "I tried, but I wasn't good enough". :)

And of course you won't be alone, any question we're here to help.

[datapythonista]

@Aya-S if you have some time in the next days, I'm happy to do the release together. I'll have to learn as much as you about it, but I'm sure we'll manage. :)

Let me know if you're interested.

[jorisvandenbossche]

The PR that is needed for the 0.24.3 release (the fix to enable pandas to be installed from source on python 2.7) is pandas-dev/pandas#28511

[Aya-S]

@Aya-S if you have some time in the next days, I'm happy to do the release together. I'll have to learn as much as you about it, but I'm sure we'll manage. :)

Let me know if you're interested.

@datapythonista this sounds like a very good deal! I couldn't bring myself to feel confident enough to attempt this at first.
how do we start :D?

[datapythonista]

That's great!

First thing would be to get a branch with the version to release. That is basically branching from 0.24.2 and adding the commit from pandas-dev/pandas#28511 (which is not yet merged).

And after that, create a new release on GitHub, create packages for pip and conda, and update the website/documentation.

But we'll practice a bit before we do it for real. Tom sent us the instructions to do the release: https://github.com/pandas-dev/pandas-release

Do you want to have a look at the document, try to do what's in there, and discuss the questions you have? There are things like pushing to git, uploading the documentation... that you won't be able to do. That's good news, because you can test as much as you want, that you won't be able to break anything. :) Just skip these steps when you find them.

Does this make sense?

[Aya-S]

That's great!

First thing would be to get a branch with the version to release. That is basically branching from 0.24.2 and adding the commit from pandas-dev/pandas#28511 (which is not yet merged).

And after that, create a new release on GitHub, create packages for pip and conda, and update the website/documentation.

But we'll practice a bit before we do it for real. Tom sent us the instructions to do the release: https://github.com/pandas-dev/pandas-release

Do you want to have a look at the document, try to do what's in there, and discuss the questions you have? There are things like pushing to git, uploading the documentation... that you won't be able to do. That's good news, because you can test as much as you want, that you won't be able to break anything. :) Just skip these steps when you find them.

Does this make sense?

ok, great. Then I'll start with the document and let you know how things go!

[Aya-S]

@datapythonista @TomAugspurger
I checked out the tag for v0.24.2
`commit cb00deb94500205fcb27a33cc1d0df79a9727f8b (HEAD -> trial_0_24_2, tag: v0.24.2)
Author: Joris Van den Bossche jorisvandenbossche@gmail.com
Date: Tue Mar 12 22:12:11 2019 +0100

RLS: 0.24.2

`

and was starting to follow the instructions but the makefile I have now, which is the following, doesn't match the instructions, seems like the checkout is not right? any idea what might be causing the discrepancy?
Thanks in advance :D
`tseries: pandas/_libs/lib.pyx pandas/_libs/tslib.pyx pandas/_libs/hashtable.pyx
python setup.py build_ext --inplace

.PHONY : develop build clean clean_pyc tseries doc

clean:
-python setup.py clean

clean_pyc:
-find . -name '*.py[co]' -exec rm {} ;

build: clean_pyc
python setup.py build_ext --inplace

lint-diff:
git diff upstream/master --name-only -- "*.py" | xargs flake8

develop: build
-python setup.py develop

doc:
-rm -rf doc/build doc/source/generated
cd doc;
python make.py clean;
python make.py html
python make.py spellcheck`

[datapythonista]

The Makefile you need to use is not the pandas one, but the one in the repo for the pandas release: https://github.com/pandas-dev/pandas-release/blob/master/Makefile

[Aya-S]

Makes sense (y) will get the right one.

…

On Sun, Sep 22, 2019, 12:49 AM Marc Garcia ***@***.***> wrote: The Makefile you need to use is not the pandas one, but the one in the repo for the pandas release: https://github.com/pandas-dev/pandas-release/blob/master/Makefile — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#166?email_source=notifications&email_token=ABUSU7UXM6AWBL6IF5HU7H3QK2QIJA5CNFSM4IVZNKE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7I25VI#issuecomment-533835477>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABUSU7VGBXZEFCIY435OHO3QK2QIJANCNFSM4IVZNKEQ> .

[Aya-S]

Hello @datapythonista !
I'm at the stage of fetching the PR to merge to the v0.24.2 tag.
i used this command:
git fetch upstream pull/28511/head:test-branch
wondering about

1. how to test if the fetch succeeded
2. how to test the codebase for coherency and make sure the PR was properly fetched

[datapythonista]

In git all repos are the same technically speaking, so you can do that with your fork to test is everything works.

But I'd move forward and check more the packaging part, I think that's the tricky part of the process, more than anything else. What do you think?