diff options
| author | Robert Adam <dev@robert-adam.de> | 2022-01-02 14:12:46 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-01-02 14:12:46 +0300 |
| commit | ef045be7fe04657e27141922000d84a144b75c26 (patch) | |
| tree | ddbfc3f2ec5af8d3f897636044cdcfbd6eccf43d /docs | |
| parent | 74057e0f5287168231ff60e9c4d616fe8a250c39 (diff) | |
| parent | 6caa808e67fe72b797fec42d9821e9e2242ca74b (diff) | |
Merge PR #5400: BUILD: Remove concept of an RELEASE_ID
Having a separate RELEASE_ID just unnecessarily complicates drafting
releases. Plus, now that we are using different build numbers for every
new build anyway, a separate release ID is really not necessary.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/dev/build-instructions/README.md | 1 | ||||
| -rw-r--r-- | docs/dev/build-instructions/find_build_number.md | 12 |
2 files changed, 13 insertions, 0 deletions
diff --git a/docs/dev/build-instructions/README.md b/docs/dev/build-instructions/README.md index 734e07edf..88cad727c 100644 --- a/docs/dev/build-instructions/README.md +++ b/docs/dev/build-instructions/README.md @@ -21,6 +21,7 @@ In order to actually build Mumble, you can follow one of the following instructi Furthermore you might find these helpful as well: - [FAQ](faq.md) +- [Determine build number](find_build_number.md) - [Common build errors](common_build_errors.md) - [List of available cmake options](cmake_options.md) - [IDE integration](ide_integration.md) diff --git a/docs/dev/build-instructions/find_build_number.md b/docs/dev/build-instructions/find_build_number.md new file mode 100644 index 000000000..93be2f3d0 --- /dev/null +++ b/docs/dev/build-instructions/find_build_number.md @@ -0,0 +1,12 @@ +# Finding the correct BUILD_NUMBER + +When invoking CMake, you can specify a build number as e.g. `-DBUILD_NUMBER=42`. The build number will be used as the third component of the Mumble +version. + +First off: This is only important if you are planning to distribute/package Mumble (it makes sure that Mumble can be upgraded properly). For +self-compiled versions this doesn't really matter and you can simply omit the build number. + +The build number is automatically increased with every commit that is made to Mumble. All build numbers for all commits can be found on +https://mumble.info/build-number.json. Simply look up the current commit hash (topmost entry in the result of `git log`) in the list and use the +corresponding build number. + |