-
-
Notifications
You must be signed in to change notification settings - Fork 1
Release Management
When you are ready to create a new release we need to update the VERSION and adapt the RELEASE_DATE variables in the upgrade-ux script:
$ cd ~/projects/upgrade-ux/opt/upgrade-ux/bin
$ vi upgrade-ux
and change VERSION=1.7 to VERSION=1.8 (as an example), and also modify the release date from RELEASE_DATE=08-Sep-2016 to RELEASE_DATE=20-Oct-2016 (also as an example).
Also, we need to commit the change in our master branch:
$ git commit -a -m 'increasing version in upgrade-ux'
$ git push
After every new version it is required to tag the master branch at GitHub as following:
$ cd ~/projects/upgrade-ux
$ ls
LICENSE README.md etc opt packaging var
$ git pull
Already up-to-date.
$ git tag -a 1.0 -m "upgrade-ux release 1.0"
$ git push --tags
Counting objects: 1, done.
Writing objects: 100% (1/1), 173 bytes, done.
Total 1 (delta 0), reused 0 (delta 0)
To [email protected]:gdha/upgrade-ux.git
* [new tag] 1.0 -> 1.0
To display the current set of tags use the command:
$ git tag
Run the autogen.sh script to re-generate the CHANGELOG.rst file. See project https://github.com/vaab/gitchangelog.git to download the autogen.sh script and how to use it.
Currently we can create a software depot for HP-UX or a Linux package (rpm or debian style). Therefore, go into directory:
$ cd ~/projects/upgrade-ux/packaging/$(uname -s)
To build a software package on HP-UX you first need to become root and then type:
# make depot
To build a package on Linux type
$ make rpm
for Linux distributions based on RPM or for Debian based systems:
$ make debian
E.g. see https://github.com/gdha/upgrade-ux/wiki/Release-Notes-v1.32