[[!toc levels=3]]
Here is an example of how the 3.4 tag ( https://github.com/IQSS/dvn/tree/3.4 ) was created and pushed to GitHub:
murphy:dvn pdurbin$ git branch
* develop
master
murphy:dvn pdurbin$ git pull
Already up-to-date.
murphy:dvn pdurbin$ git checkout master
Switched to branch 'master'
murphy:dvn pdurbin$ git merge develop
Updating fdbfe57..6ceb24f
(snip)
create mode 100644 tools/installer/dvninstall/readme.md
murphy:dvn pdurbin$ git tag
3.3
murphy:dvn pdurbin$ git tag -a 3.4 -m 'merged develop, tagging master as 3.4'
murphy:dvn pdurbin$ git tag
3.3
3.4
murphy:dvn pdurbin$ git push origin 3.4
Counting objects: 1, done.
Writing objects: 100% (1/1), 182 bytes, done.
Total 1 (delta 0), reused 0 (delta 0)
To git@github.com:IQSS/dvn.git
* [new tag] 3.4 -> 3.4
murphy:dvn pdurbin$
murphy:dvn pdurbin$ git push
Total 0 (delta 0), reused 0 (delta 0)
To git@github.com:IQSS/dvn.git
fdbfe57..6ceb24f master -> master
murphy:dvn pdurbin$
On dvn-build:
cd tools/installer
mkdir dvninstall/config
mkdir dvninstall/appdeploy/dist
make installer
Rename the resulting "dvninstall.zip" to include the release number (i.e. "dvninstall_v3_4.zip") and upload it, the separate war file, a readme, and a buildupdate script (all these files should include the release number) to SourceForge (i.e. http://sourceforge.net/projects/dvn/files/dvn/3.4/ ).
The file to edit is https://github.com/IQSS/dvn/blob/develop/src/DVN-web/src/VersionNumber.properties