...
| Code Block | ||
|---|---|---|
| ||
RC_VERSION=1.1011.0 |
Using the above variable, complete the below git commands for each module being released. The modules to be released are shown in the VIVO modules release plan. A new tab may need to be added for this release. When the steps below are complete for a specific module, change the color to green, so that others know what's been done.
...
| Code Block |
|---|
git checkout <develop -or- maintenance-branch> git pull git push origin <develop -or- maintenance-branch>:$relrel-${RC_VERSION}-RC |
Tag the release candidate branch
| Code Block |
|---|
git checkout ${RC_VERSION}-RC
git tag -a "rel-${RC_VERSION}-RC-1" -m "rel-${RC_VERSION}-RC-1" -m "rel-${RC_VERSION}-RC-1"
git push origin --tagsRC_VERSION}-RC-1"
git push origin --tags |
Script Example for Linux or MINGW64 on Windows:
| Code Block |
|---|
#!/bin/bash
# RC Script
RC_VERSION=1.11.0
RC_NUM=1
git checkout develop
git pull
git push origin develop:rel-${RC_VERSION}-RC
git checkout rel-${RC_VERSION}-RC
git tag -a "rel-${RC_VERSION}-RC-${RC_NUM}" -m "rel-${RC_VERSION}-RC-${RC_NUM}"
git push origin --tags
# Created Branch and Tag Examples
# (Branch) https://github.com/vivo-project/VIVO/tree/rel-1.11.0-RC
# (Tag) https://github.com/vivo-project/VIVO/tree/rel-1.11.0-RC-1
# (Branch) https://github.com/vivo-project/Vitro/tree/rel-1.11.0-RC
# (Tag) https://github.com/vivo-project/Vitro/tree/rel-1.11.0-RC-1 |
Some of the previous steps can be done directly into github interface as described in following tutorials:
...
| Note | |||||||
|---|---|---|---|---|---|---|---|
Your GPG passphrase may not be masked in terminal.
|
Inspect/Verify local updates:
...
| Code Block |
|---|
git push origin --tags # mvn task relies on the tag, make sure it does not collide with a branch name |
...
Go to
https://github.com/vivo-project/$REPO/releases/- Click "Draft a new release", and update title to "Release $CURR"
- Attach appropriate artifacts
- Attach artifact MD5 files (e.g. artifact = jena2tools-1.2.0.jar, MD5 = jenatools-1.2.0.jar.md5)
If appropriate, attach binaries and checksums that have been published to Maven Central- Click Publish Release
...
Push Release Branch to develop and 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.
- Changing from SNAPSHOT version to release version. Something like [maven-release-plugin] prepare release $REPO-$CURR
- 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.
...