v2.4 release

[alimanfoo]

Raising this for discussion of a 2.4 release. There's lots been done since the last release. Any nominations for outstanding PRs we should try to get done before making a release? Or shall we release now and then try to keep up momentum and get into a more regular release rhythm?

Also this will be the first release to drop support for Python 2. Can we still make this a minor version bump (2.3.2 -> 2.4.0) or do we need a major version bump?

[joshmoore]

I'd vote for a minor bump. The imminent death of py2 doesn't seem to be sufficient cause for all packages to undergo a major bump.

[jrbourbeau]

Re: when to release, I'm in favor of releasing now and then trying to keep a more regular release cycle. Our master branch seems quite stable, so we could probably release at a higher cadence without much additional effort.

I'm also in favor of a minor bump to 2.4.0.

[chris-allan]

Definitely in favor of a release soon. Not having #485 in a release is causing us to have to install from a Git hash which we have been doing since early November and I would really like to stop.

Just going to 2.4.0 seems fine.

[alimanfoo]

OK, let's make a release and call it 2.4.0. @jrbourbeau would you be willing and able to do the honours?

Might also be a good opportunity to review and update the documentation on how to make a release. Doesn't seem necessary to do a local tox run any more before releasing, CI should be catching any problems before PRs are merged. Also we could automate the pypi release via travis, which would mean releasing is as simple as creating a new release on github.com. Would be happy if anyone has best practice advice, I may be behind the times.

[jakirkham]

Any chance we can squeeze in PR ( #450 )? Would be nice to fix the tree visualization in JupyterLab. Though no worries if not 😉

[jrbourbeau]

Yeah, I'm happy to push out a new release. I'll make sure to open up a PR so others can review before tagging a release. @alimanfoo or @jakirkham could you please add me on PyPI, my username is the same as on GitHub.

[jakirkham]

Ok you should have permissions on PyPI. Also making sure you are added to the conda-forge feedstocks as well.

[jrbourbeau]

Great, thanks @jakirkham!

[jrbourbeau]

Closing as 2.4.0 is on PyPI and conda-forge. Big thanks to all who contributed!

[jakirkham]

Thanks for working on this @jrbourbeau! 😀

[jakirkham]

WDYT about doing a blogpost on 2.4.0?