dev:release_process:evergreen:how_to_build
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
dev:release_process:evergreen:how_to_build [2024/05/16 10:52] – [Upload to web server (requires access to the evergreen-ils.org web server)] gmcharlton | dev:release_process:evergreen:how_to_build [2024/05/28 09:59] (current) – Correcting the .0 release instruction bmagic | ||
---|---|---|---|
Line 185: | 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 |
dev/release_process/evergreen/how_to_build.txt · Last modified: 2024/05/28 09:59 by bmagic