allow branches / test if it already works

[abma]

-> Anarchid

[abma]

maybe do it like that:

make the update-script check which local branches exist and for every branch do:

• check if local branch is updated
• if updated, create new rapid tag name:branch:version (skip branch: for master branch?!)

[abma]

currently: Spring: 1944 dev-test-3488-0502296 -> with branches: Spring: 1944 dev-branchname-3488-0502296 ?!

VERSION{} is only handled in master branch ?!

[abma]

when doing this:

rewrite the update script in python

[Anarchid]

(18:30:23) Anarchid: (and to summarize the proposed system)
(18:31:03) Anarchid: so: master is the magical branch from which releases are possible with VERSION commits; every other branch is built with e.g.zk:branch:test:commitnum-gcommithash or just zk:branch:commitnum-gcommithash
(18:31:36) Anarchid: master also gets built from each commit into zk:master:commitnum:commithash, but commits with VERSION are built into zk:stable:$VERSION
(18:32:04) Anarchid: this does allow for cherry-picking, so i'm satisfied
(18:32:21) abma_irc: in the master branch, "master:" is removed
(18:32:37) Anarchid: so zk:test vs zk:featurebranch:test
(18:32:48) Anarchid: sounds legit
(18:32:50) abma_irc: so current tags stays the same

[PicassoCT]

So it's only possible from master