...
- fcrepo-build-tools: if schedule for a release, must be handled first since it's version number is present in the other modules
- fcrepo4: the main project, always part of a release, takes the vast majority of the time (also push gh-pages)
- fcrepo-message-consumer (also push gh-pages)
- fcrepo-module-auth-rbacl (also push gh-pages)
- fcrepo-module-auth-xacml (also push gh-pages)
- fcrepo-camel (also push gh-pages)
- ontology (no push to sonatype)
- --- labs below
- fcrepo4-client (also push gh-pages)
- fcrepo-audit (also push gh-pages)
- fcrepo-camel-toolbox (also push gh-pages)
- ----
- fcrepo-webapp-plus (no push to sonatype)
- fcrepo4-release-tests (ditto)
- fcrepo4-oaiprovider (ditto)
- fcrepo4-swordserver (ditto)
- migration-utils (ditto)
- ---
- fcrepo4-vagrant (update versions)
Merge the release candidate branch into master (if any commits were made)
...
- Write a description
Create MD5 and SHA1 files for each of the release artifacts
Code Block title compute-checksums.sh for x in `ls *.war`; do echo $x; md5sum $x > ${x}.md5; sha1sum $x > ${x}.sha1; done- Upload artifacts to GitHub release (war, war.md5, war.sha1)
- See the artifacts found in "Downloads" to know which need to be uploaded to GitHub
Complete the Duraspace wiki documentation updates
...