Page History
...
- Checkout the Language Pack Module:
git clone git
@github
.com:DSpace/dspace-api-lang.git dspace-api-lang
cd dspace-api-lang
git checkout master
NOTE: always release language packs from the master branch, we do not use a maintenance branch for language packs.
- Do a Dry Run:
mvn release:prepare -DdryRun=true
- Tag and Increment Version:
mvn release:prepare -Dresume=false
- Make sure to assign a version number of the format:
[major].[minor].[sequence-number]
(e.g. 3.0.0, 3.0.1, etc for 3.0 releases of language packs) - NOTE: The release process should suggest the correct version number by default
- Make sure to assign a version number of the format:
- Deploy Artifacts to Staging in Sonatype:
mvn release:perform
- Verify and Release Staged Artifacts in Sonatype (see instructions at link)
- Go back and run steps #1-5 above for the other language packs modules (dspace-xmlui-lang)
...
Note: do not just re-use an old working copy of the DSpace Master branch, for obvious reasons, you don't want your own work in progress sneaking into the release. It's also important to use the SSH repository path as noted above (NOT the https URL), otherwise you will be prompted for your GitHub credentials during the release process. More than once. Save yourself some time, be sure to use the SSH path.
Note: if you are doing a maintenance release, you will need to check out the maintenance branch, and not the master branch. In this case, the example above would instead read:
Code Block |
---|
git clone git@github.com:DSpace/DSpace.git ~/dspace-release
cd ~/dspace-release
git checkout dspace-3_x
(or whatever the current maintenance branch might be named) |
Update your Local Maven Cache (optional)
...
Overview
Content Tools