dev:release_process:evergreen:how_to_build
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
dev:release_process:evergreen:how_to_build [2024/05/13 15:39] – [Run the release builder script] aneiman | dev:release_process:evergreen:how_to_build [2024/05/28 09:59] – Correcting the .0 release instruction bmagic | ||
---|---|---|---|
Line 60: | Line 60: | ||
$ find . -mindepth 2 -name ' | $ find . -mindepth 2 -name ' | ||
$ find . -mindepth 2 -name ' | $ find . -mindepth 2 -name ' | ||
+ | $ echo "" | ||
</ | </ | ||
Line 184: | Line 185: | ||
* Use the highest numbered previous version for the second version value. | * Use the highest numbered previous version for the second version value. | ||
* For example, building 3.13-beta, the script should start from the highest 3.12 release at the time of branching: <code bash>$ build/ | * For example, building 3.13-beta, the script should start from the highest 3.12 release at the time of branching: <code bash>$ build/ | ||
- | * For a .0 release, the script should start from (probably) | + | * For a .0 release, the script should start from the highest point release |
* For a point release, the script should start from the previous point release in the series: <code bash>$ build/ | * For a point release, the script should start from the previous point release in the series: <code bash>$ build/ | ||
* Use the -v flag when your branch name does not match the normal pattern, otherwise auto-detect works | * Use the -v flag when your branch name does not match the normal pattern, otherwise auto-detect works | ||
Line 229: | Line 230: | ||
* Release notes go in ''/ | * Release notes go in ''/ | ||
+ | Because the release notes document is cumulative for each release series, a symbolic link exists for each release series so that (e.g.) '' | ||
+ | |||
+ | When updating the downloads page to the website, the URL should use the symbolic link, not the release notes for the specific release, e.g., '' | ||
==== " | ==== " | ||
dev/release_process/evergreen/how_to_build.txt · Last modified: 2024/07/18 09:17 by sandbergja