Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Preparation for 4.0.0rc0. As noted in #1078, the prospect of many deprecations needing to be double-checked has slowed down my ability to make this release happen. It still needs to happen, and it should start with a release candidate.
We've jumped a few numpy versions and dropped Python 3.6, and we have some improvements that will make things easier for downstream projects.
I think let's aim for next Monday to give everyone time to polish off enhancement/new feature PRs. Additional bug fixes can come post-release.
Pre-release checklist
doc/source/index.rst
and add any authors not yet acknowledged..mailmap file
if there are any duplicate authors listed fromgit shortlog -nse
.LONG_DESCRIPTION
ininfo.py
by runningmake refresh-readme
.setup.cfg
(e.g.,install_requires
,options.extras_require
) and indoc/source/installation.rst
and inrequirements.txt
and.travis.yml
. They should at least match. Do they still hold? Make sure nibabel on travis is testing the minimum dependencies specifically.pytest --doctest-modules nibabel
Adapted from http://nipy.org/nibabel/devel/make_release.html#release-checklist