Release Process

Overview

Needs work

TODO: Add more information to each of these

In general, work is carried out in the development branches of the main NeuroML repositories and these are merged to master branches on a new major release, e.g. move from NeuroML v2.1 to v2.2.

Steps for new major release

These are the steps required for a new release of the NeuroML development tools.

Task

Version this was last done

Tag previous development versions of individual repos

v2.1

Increment all version numbers - to distinguish release from previous development version

v2.1

Commit all work in development branches

v2.1

Test all development branches - rerun Travis-CI at least once

v2.1

Recheck all READMEs & docs

v2.1

Run & check test.py in NeuroML2 repo

v2.1

Check through issues for closed & easily closable ones

v2.1

Update NeuroML milestones

v2.1

Update HISTORY.md in NeuroML2

v2.1

libNeuroML: Update README; Retest; Merge to master; Tag release; Release to pip; Check installation docs

v2.1

pylems: Update README; Merge to master; Tag release; Release to pip

v2.1

pyNeuroML: Update Readme; Tag release; Release to pip

v2.1

Java repositories (jNeuroML, org.neuroml.* etc.): Merge development to master; Tag releases

v2.1

Rebuild jNeuroML & commit to jNeuroMLJar

v2.1

Regenerate Cells.xml etc. on nml website & commit

v2.1

Update docs on http://www.neuroml.org

v2.1

Add new binary release on https://github.com/NeuroML/jNeuroML/releases

v2.1

ANNOUNCE (mailing list, Twitter)

v2.1

Increment version numbers in all development branches

v2.1

DOI on Zenodo

v2.1

New milestone in issues

v2.1

Update version used in neuroConstruct

v2.1

New release of neuroConstruct

v2.0

Test toolchain on Windows…

v2.0