Browse Source

More release process notes

pull/112/head
Jonathan "Duke" Leto 2 years ago
parent
commit
a00b1d604a
  1. 11
      doc/release-process.md

11
doc/release-process.md

@ -49,9 +49,16 @@ git push
* Merge dev branch into master
* Make a new Gitea release from master branch
* There is an option for Gitea to automate making a new Git tag as well
* SD requires to be build with a staticly compiled version of QT for release binaries
* SD requires a staticly compiled version of QT for release binaries
* If it isn't, the binary will resort to using the system QT which is usually a different version and the binary will not work
* Make linux binaries: `./src/scripts/make-binary-tarball.sh`
* Make linux binaries:
```
# QT_STATIC is a directory with a staticly compiled qt5.x
# HUSH_DIR is a directory containing hushd/hush-cli binaries
# APP_VERSION is the version being released in git tag format (prepended v), such as v1.3.1
QT_STATIC=$HOME/src/qt5 APP_VERSION=vX.Y.Z HUSH_DIR=$HOME/git/hush3 src/scripts/mkrelease.sh
```
* Make linux binary tarball: `./src/scripts/make-binary-tarball.sh`
* Upload to gitea release
* Make debian package with `./src/scripts/make-deb.sh`
* Upload to gitea release

Loading…
Cancel
Save