| LLVM Release Wrapper Script |
| =========================== |
| |
| UPDATE: These scripts are outdated and may not reflect the current way to run |
| the release. The official way to run LLVM releases at Linaro now are |
| through Jenkins job: |
| |
| https://ci.linaro.org/job/tcwg-llvm-release/ |
| |
| See also: |
| |
| https://collaborate.linaro.org/display/LLVM/LLVM+Release+Process |
| |
| =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= |
| |
| The LLVM release is done using the test-release.sh script available on LLVM's |
| sources, directory utils/release. But the options may change, and to keep track |
| of how we release LLVM for ARM and AArch64, I wrote a simple script that |
| remembers what were the options. |
| |
| This allows one to quickly setup a machine to produce a release, which can be |
| used for testing, validation, or replacement of a broken release machine. But |
| also keeps track of how we released LLVM throughout the years, beginning with |
| release 3.7.0. |
| |
| Usage is simple. With test-release.sh on the same directory, just call: |
| |
| $ nohup ./run 3.N.M RC & |
| |
| With N as major version, M as minor and RC as release candidate, which is |
| normally 1, 2, 3, final. |