-
Notifications
You must be signed in to change notification settings - Fork 12
Releasing BoneJ
Alessandro Felder edited this page Apr 17, 2019
·
28 revisions
This is a check list of things to do before releasing a new version(s) of the BoneJ Maven artefacts.
- Code that has become obsolete has been
@Deprecated
-
@Deprecated
code carried over from previous versions has been removed - TODOs minimized.
- Update all dependencies with explicit version numbers if needed
- Make necessary changes, or mark for resolving later (e.g. newly deprecated code)
- Check that code compiles and test pass (
mvn clean package
)- Run slow tests for
wrapperPlugins
too (mvn test -P allTests
). They may fail due to time outs. Check that they don't fail repeatedly.
- Run slow tests for
- Check that dependencies are correctly marked (
mvn dependency:analyze
shows no warnings) - Check Javadoc is OK (
mvn javadoc:javadoc
) - Carefully initiate the "double push"
- Update artefact versions to stable according to semantic versioning
- Comment out modules that don't get released
- Also update the parent artefacts
- Double check that parents list correct module numbers, and affected modules the correct parents
-
git push
to master
- Check that Travis build passes
- Complete the "double push"
- Update affected artefacts to next
SNAPSHOT
versions - Activate modules previously commented out
- Also update pom parents to next
SNAPSHOT
- Double check artefact numbers
- Update affected artefacts to next
- Update documentation
- Release notes on the developer Wiki
Additionally if you want to make this a new user release
- Tag the commit where artefact(s) were released
- Draft a release, following the style in prior releases
- Check that Zenodo has archived the release code
- Ensure that the user docs are up to date
- Update the imagej.net Wiki with a redirect for new plugins
- Upload new artefact(s) to the update site.
- Announce the release on the forum and Twitter