Page History

...

This will publish the artifacts to the Sonatype releases repository and start the process of syncing them with Maven Central, which may take several hours. When finished, they'll be available at https://repo1.maven.org/maven2/org/fcrepo/.

Docker Release (fcrepo only)

From the cloned fcrepo repository home run the following:

git clone git@github.com:fcrepo-exts/fcrepo-docker.git
cd fcrepo-docker
DOCKER_PASSWORD=<password> DOCKER_USERNAME=<username> ./build-and-push-to-dockerhub.sh ../fcrepo-webapp/target/fcrepo-webapp-${CURR}.war latest ${CURR}

Github Release - part 2

• Go to https://github.com/fcrepo4/$REPO/releases/tag/fcrepo-$CURR

• Click Edit tag, and update title to "Release $CURR"
• Attach fcrepo-webapp-$CURR binaries and checksums that have been published to Maven Central to the Github release
  
  • e.g. https://repo1.maven.org/maven2/org/fcrepo/fcrepo-webapp/5.0.2/

• Build the fcrepo-webapp-$CURR-jetty-console.jar for the release using

  Code Block
  mvn clean install -Pone-click -pl fcrepo-webapp

  
  

• Create checksums for the fcrepo-webapp-$CURR-jetty-console and attach the binary and checksums to the Github release.

  • Note: The checksum files should be of the format "[checksum] [filename]" (MacOSX's md5 requires the use of the -r argument to produce the correct format. I.e. md5 -r fcrepo-webapp-5.0.2-jetty-console.jar >> fcrepo-webapp-5.0.2-jetty-console.jar.md5).

    Code Block
    jarPath=fcrepo-webapp/target/fcrepo-webapp-$CURR-jetty-console.jar md5 -r ${jarPath} > ${jarPath}.md5 shasum ${jarPath}> ${jarPath}.sha1

    
    

• Click Publish Release

...

Push Release Branch to Maintenance

...

The release branch has changes made since code freeze. It also contains the update to the version numbers for future development.

...

Ensure that your commit history matches the release branch's commit history, except for the two additional commits.
 

1. Changing from SNAPSHOT version to release version. Something like [maven-release-plugin] prepare release $REPO-$CURR
2. Changing from release version to next development version. Something like [maven-release-plugin] prepare for next development iteration

...

If this appears correct, you can push your release branch on to the maintenance branch.

...