Checklist of Elements That Need to Be Updated Each Release

1. Zenodo Badge in Readme
2. Configuration YAML examples in configs
3. The AMI

• Log into the fcp-indi account.
• Make sure that /media/ebs and /mnt exist and are configured with the correct permissions.
• Update nipype.
• Update C-PAC.
• Update AFNI using @update.afni.binaries.
• Run apt-get update to check for updates for repo-based dependencies.
• Run a test subject- copy results back to local drive for use as pre-computed outputs.
• Test X2Go. Make sure that launcher on desktop is properly sourcing bashrc.
• Update AMI code in cloud documentation (for Starcluster cluster definition).
• Create two AMIs for AWS. Make one AMI public (for Starcluster) and another AMI that will be private (for Amazon Marketplace). For the Amazon Marketplace AMI, navigate to https://aws.amazon.com/marketplace/management/manage-products and share the AMI. Then, navigate to https://aws.amazon.com/marketplace/management/product-load/, download the product load form, fill it out, and re-upload it.
• Check to make sure that only one set of Python dependencies exists (Neurodebian installs packages to /usr/lib/python2.7/dist-packages, while pip/setup.py install to /usr/local/lib/python2.7/dist-packages).
• Make sure that new dependencies are added.
• Make sure that AMI is public.

4. The documentation must be merged from dev to master.
5. The in-app documentation must be updated. Images must be ensured to be compatible with the latest version of libpng (see: https://github.com/spyder-ide/spyder/pull/2216 )
6. The releases page must be have binaries uploaded to it (whose downloads will be tracked by the GitHub API.
7. The download links on the FCP-INDI website must be updated.
8. The C-PAC benchmark must be updated.

• Pipeline configuration must be updated.
• Results must be re-run with the new release.
• Download links must be updated.