2.2.0 release prep

[effigies]

Minor version increment. Fixed a FreeSurfer test that depended on FreeSurfer < v6.0.0.

Closes #540

Open issues/PRs that could go in quickly

• Transition FutureWarnings older than X versions to Deprecations? #524
• ENH: Add image slicing #550
• streamlines module can't be found #554
• Only use indexed_gzip when explicitly requested #562
• Follow-up edits to Conditionally use indexed_gzip #552 (comment)?

Pre-release checklist

• Review the open list of nibabel issues. Check whether there are outstanding issues that can be closed, and whether there are any issues that should delay the release. Label them!
• Review and update the release notes. Review and update the Changelog file.
• Look at doc/source/index.rst and add any authors not yet acknowledged.
• Use the opportunity to update the .mailmap file if there are any duplicate authors listed from git shortlog -nse.
• Check the copyright year in doc/source/conf.py
• Refresh the README.rst text from the LONG_DESCRIPTION in info.py by running make refresh-readme.
• Check the dependencies listed in nibabel/info.py (e.g. NUMPY_MIN_VERSION) and in doc/source/installation.rst and in requirements.txt and .travis.yml. They should at least match. Do they still hold? Make sure nibabel on travis is testing the minimum dependencies specifically.
• nibabel-release-checks
  • make sdist-tests errors
  • make check-version-info
  • make check-files
  • make -C doc doctest
  • python -m compileall .
  • make source-release
• Make sure all tests pass (from the nibabel root directory): nosetests --with-doctest nibabel
• Edit nibabel/info.py) to set _version_extra to ''; commit
• Build bots
  • nibabel-py2.7-osx-10.10
  • nibabel-bdist32-27
  • nibabel-bdist32-33
  • nibabel-bdist32-34
  • nibabel-bdist32-35
  • nibabel-bdist64-27

Adapted from http://nipy.org/nibabel/devel/make_release.html#release-checklist

[codecov-io]

Codecov Report

Merging #555 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #555      +/-   ##
==========================================
+ Coverage   94.32%   94.32%   +<.01%     
==========================================
  Files         177      177              
  Lines       24689    24691       +2     
  Branches     2638     2638              
==========================================
+ Hits        23288    23290       +2     
  Misses        925      925              
  Partials      476      476

Impacted Files	Coverage Δ
nibabel/freesurfer/tests/test_io.py	91.83% <100%> (+0.11%)	⬆️
nibabel/info.py	100% <100%> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8c1d0bc...2ca6848. Read the comment docs.

[coveralls]

Coverage increased (+0.0003%) to 96.271% when pulling 439201c on rel/2.2.0 into dbe74e1 on master.

[coveralls]

Coverage increased (+0.0003%) to 96.271% when pulling 274a6ce on rel/2.2.0 into dbe74e1 on master.

[effigies]

@matthew-brett Do you have time to look at the make sdist-tests errors? Looking at the code, I don't see why those failed.

Apart from open issues to decide whether to work on, that's the only hang-up I have for release.

[coveralls]

Coverage increased (+0.0003%) to 96.269% when pulling 0a489d4 on rel/2.2.0 into fa76141 on master.

[coveralls]

Coverage increased (+0.0003%) to 96.254% when pulling 2ca6848 on rel/2.2.0 into 8c1d0bc on master.

[effigies]

Now two failing chunks of nibabel-release-checks. Any thoughts? I've tried updating the np.printoptions in nifti_images.rst, but that didn't resolve the issue.

[effigies]

@matthew-brett Stuck here. If you can find some time, I could use some help getting this release out.

[matthew-brett]

Sorry Chris - got a bit snowed under. Sorry too, I should have deleted those from the release doc - when I wrote those checks, we were doing much much less automated testing - and they were before we had scripts being testing. So I think we can ignore those errors. And we should remove those checks.

[effigies]

Sounds good. I'll merge this and release today, if there are no other issues.

[matthew-brett]

Are you planning to release without the image slicing? I can try to get to this later today.

[effigies]

Can go either way. Obviously would be a nice feature to have, but if you think it needs more time to settle the API and test before it's in an official release, that's fine too.

If you want to see how close it is to ready, we can decide whether to put it in first.

[matthew-brett]

Let's leave the image slicing for the next release - and plan for another release in a month or so?

[effigies]

Sounds good.