...
If any online resources have been modified or added to during the release, these must be updated.
Release Day
Determine which modules will be released.
Of the projects in https://github.com/fcrepo4. which should be released. Typically we keep the release versions in sync for those that have had a formal release.
Release Order
Due to dependency chains, the following release order is required. Furthermore, the artifacts of dependencies must be propagated to maven central before the next one can be released.
- 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
- fcrepo-jms-indexer-pluggable
- fcrepo-module-auth-xacml
- fcrepo-sample-dataset
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 export RELEASE_VERSION=4.0.0-beta-01 sha1sum fcrepo-webapp-$RELEASE_VERSION.war |cut -f1 -d' ' > fcrepo-webapp-$RELEASE_VERSION.war.sha1 md5sum fcrepo-webapp-$RELEASE_VERSION.war |cut -f1 -d' ' > fcrepo-webapp-$RELEASE_VERSION.war.md5 sha1sum fcrepo-webapp-$RELEASE_VERSION-jetty-console.war |cut -f1 -d' ' > fcrepo-webapp-$RELEASE_VERSION-jetty-console.war.sha1 md5sum fcrepo-webapp-$RELEASE_VERSION-jetty-console.war |cut -f1 -d' ' > fcrepo-webapp-$RELEASE_VERSION-jetty-console.war.md5 sha1sum fcrepo-webapp-$RELEASE_VERSION-auth.war |cut -f1 -d' ' > fcrepo-webapp-$RELEASE_VERSION-auth.war.sha1 md5sum fcrepo-webapp-$RELEASE_VERSION-auth.war |cut -f1 -d' ' > fcrepo-webapp-$RELEASE_VERSION-auth.war.md5
- Upload artifacts to GitHub release (war, war.asc, war.md5, war.sha1)
Release related projects
Release other projects that are related to the main codebase, following the same process as outlined above.
...
Complete the Duraspace wiki documentation updates
...