clarifying release process and version numbers

[pocock]

I see there is a beta release 4.11005 available for download. The download page says it was released 2019-07-14

http://www.domoticz.com/downloads/

The downloads are all binaries, is there a source tarball for 4.11005? I want to test a package built from source to see if there are any issues with the beta

What is the relationship between the number 11005 and the commit in Git that was used for the build? How do you generate these version numbers?

Do you normally tag the betas? It would be really helpful for people who want to find them. You can put multiple tags on a single commit, so you could tag it as beta/4.11005

git tag -s -m 'Tag a beta' beta/4.11005 $SOME_COMMIT_ID

and then if everybody is happy with the beta, tag it again

git tag -s -m 'Tag a release' 4.11005 $SOME_COMMIT_ID


I saw some scripts in the repository for helping build a release. Could you include a RELEASE_PROCESS.txt file or something similar giving step-by-step instructions, e.g. how you create the version number, updating the History.txt, which scripts you run. This will help anybody else who wants to help improve the release process, packaging and related tooling.

I will probably test the packaging of both Domoticz and the Zigate plugin again one night this week and give feedback.

Thanks for your efforts with this project.