Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Current »

This was the procedure used to release the 7.0 beta1 release.  It may change prior to 7.0 final.

0. Select a Release Tag Name

Something like "dspace-7.0-beta1".  We will use this same tag for the Backend, Frontend and DockerHub.

1. Release Backend Via Maven

  • Generally, follow the existing Official Release Procedure at Release Procedure#MakinganOfficialRelease(e.g.'dspace-x.y'or'dspace-x.y-rc1')
    • Make sure to add "-Drelease" on each command.  This property ensures the proper Maven modules are enabled (or disabled) based on what needs to be released.
    • Dry Run:   mvn release:prepare -DdryRun=true -Drelease
      • Release Version: "7.0-beta1"
      • Release Tag: "dspace-7.0-beta1"
    • Tag & Increment Version:  mvn release:prepare -Dresume=false -Drelease
    • Deploy to Sonatype:   mvn release:perform -Drelease
    • Login to Sonatype & release to Maven Central: http://oss.sonatype.org/
  • Create a Release in GitHub linking to the Release Notes

2. Release Frontend Via a Tag

3. Build Docker Images for Tagged Releases

Images can be built & pushed from commandline to DockerHub.  Again, use the same tag name as above.

Terry, Tim, Kim & Pascal currently have Push access.  Request it from one of them if you don't have it yet.

Build docker image
cd <DSPACE-SRC>
--checkout tag--
docker build -t dspace/dspace:<tag> .
docker push dspace/dspace:<tag>

cd <ANGULAR-SRC>
--checkout tag--
docker build -t dspace/dspace-angular:<tag> .
docker push dspace/dspace-angular:<tag>
  • No labels