| Renato Golin | 94cc104 | 2016-04-26 11:02:23 +0100 | [diff] [blame] | 1 | LLVM Release Wrapper Script |
| 2 | =========================== |
| 3 | |
| Renato Golin | 5985023 | 2017-05-30 16:53:47 +0100 | [diff] [blame] | 4 | UPDATE: These scripts are outdated and may not reflect the current way to run |
| 5 | the release. The official way to run LLVM releases at Linaro now are |
| 6 | through Jenkins job: |
| 7 | |
| 8 | https://ci.linaro.org/job/tcwg-llvm-release/ |
| 9 | |
| 10 | See also: |
| 11 | |
| 12 | https://collaborate.linaro.org/display/LLVM/LLVM+Release+Process |
| 13 | |
| 14 | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= |
| 15 | |
| Renato Golin | 94cc104 | 2016-04-26 11:02:23 +0100 | [diff] [blame] | 16 | The LLVM release is done using the test-release.sh script available on LLVM's |
| 17 | sources, directory utils/release. But the options may change, and to keep track |
| 18 | of how we release LLVM for ARM and AArch64, I wrote a simple script that |
| 19 | remembers what were the options. |
| 20 | |
| 21 | This allows one to quickly setup a machine to produce a release, which can be |
| 22 | used for testing, validation, or replacement of a broken release machine. But |
| 23 | also keeps track of how we released LLVM throughout the years, beginning with |
| 24 | release 3.7.0. |
| 25 | |
| 26 | Usage is simple. With test-release.sh on the same directory, just call: |
| 27 | |
| 28 | $ nohup ./run 3.N.M RC & |
| 29 | |
| 30 | With N as major version, M as minor and RC as release candidate, which is |
| 31 | normally 1, 2, 3, final. |