aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRenato Golin <renato.golin@linaro.org>2017-05-30 16:53:47 +0100
committerRenato Golin <renato.golin@linaro.org>2017-05-30 16:53:47 +0100
commit59850232b751443cfefd07460fe866be301c0407 (patch)
tree3913bde40c5e575ff6af8b6afe210edfe0635d0d
parent51d2ca2aabf99a1c80cd9e87a016dc386926241f (diff)
downloadlinaro-scripts-59850232b751443cfefd07460fe866be301c0407.tar.gz
Update release readme to point to Jenkins
Change-Id: I6c84a24d6399dd8efa228aadae7132b5b96cc3ab
-rw-r--r--release/README.txt12
1 files changed, 12 insertions, 0 deletions
diff --git a/release/README.txt b/release/README.txt
index 1bf265e..18570f0 100644
--- a/release/README.txt
+++ b/release/README.txt
@@ -1,6 +1,18 @@
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