commit 8969c145752b83a42aa0de806c3e04d6708a7b69
parent 48ae94eb474602bb0170f03e0c026555ef637a49
Author: Joris Vink <joris@coders.se>
Date: Mon, 21 Mar 2022 14:22:46 +0100
Add a quick and dirty release procedure.
Mostly for myself so I remember the goodies.
Diffstat:
RELEASE | 31 +++++++++++++++++++++++++++++++
1 file changed, 31 insertions(+), 0 deletions(-)
diff --git a/RELEASE b/RELEASE
@@ -0,0 +1,31 @@
+Kore release procedure:
+
+$next = next release
+$prev = previous release
+
+kore:
+ $ git checkout 4.x-releng
+ $ git merge master
+ [update RELEASE, README.md]
+ $ git commit -a -m "update for $next"
+ $ git tag -a $next -m "Kore $next"
+ $ git archive --format=tgz --prefix=kore-$next/ -o ~/kore-$next.tgz $next
+ $ minisign -S -c "Kore $next release" -m kore-$next.tar.gz
+ $ shasum -a256 kore-$next.tar.gz > kore-$next.tar.gz.sha256
+ $ git push --tags origin 4.x-releng
+ $ git push --tags github 4.x-releng
+
+kore-site:
+ $ cp ~/kore-$next* webroot/releases
+ $ cp webroot/releases/$prev.html webroot/releases/$next.html
+ [update all relevant links]
+ [write changelog on release page]
+ $ git add webroot && git commit -a -m "update to $next"
+ $ git push origin master
+
+ [on nightfall]
+ $ cd kore-site && git pull origin master && make install-docs
+
+kore-docker:
+ $ cp -R $prev $next
+ $ ./build.sh $next