REL: 3.0.0rc1

[effigies]

Preparation for 3.0.0 Release Candidate 1, targeting Monday, October 28.

This will mark a feature freeze for Nibabel 3.0, so there will be a strong inclination to delay for features that are being actively completed. Bug fixes will be accepted between the release candidate and the final release.

• NF: GiftiImage method agg_data to return usable data arrays #793 (Submitter: @htwangtw)
• Fixing ArraySequence functionalities #811 (Submitter: @MarcCote)

Please comment to flag any other issues that should be addressed. There is the 3.0.0 RC1 milestone but a few of them are pretty stale, and I don't have the bandwidth to push them, so they're very likely to get dropped in this cycle.

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 setup.cfg (e.g., install_requires, options.extras_require) 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.
• Make sure all tests pass (from the nibabel root directory): nosetests --with-doctest nibabel
• Edit nibabel/info.py to set _version_extra to ''; commit

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

[effigies]

@yarikoptic I needed to patch versioneer again (cf. #816) to deal with the branch name here. Do you think we should fully fork versioneer in a nipy/versioneer repository?

[codecov]

Codecov Report

Merging #829 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #829   +/-   ##
=======================================
  Coverage   90.09%   90.09%           
=======================================
  Files          98       98           
  Lines       12450    12450           
  Branches     2188     2188           
=======================================
  Hits        11217    11217           
  Misses        883      883           
  Partials      350      350

Impacted Files	Coverage Δ
nibabel/_version.py	100% <ø> (ø)	⬆️
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 b773576...cfa1cb4. Read the comment docs.

[effigies]

@djarecka @chrisgorgo I grabbed your Zenodo entries from Nipype, but bumped Chris' affiliation to Google. Please let me know if you'd like these changed before the final release.

[djarecka]

@effigies - thanks for adding. However, I've just realized that this is not my number (yes, it's the same as in nipype - it must have been copied from "Ziegler, Erik", I'll correct it today)
My number is: 0000-0001-8282-2988

[effigies]

Yikes. Good catch.