Merge pull request #42 from bazelbuild:update-release.md
PiperOrigin-RevId: 351128564
Change-Id: I5c6e9720c2ff828fab2e0870dc471387947eb6b3
diff --git a/AUTHORS b/AUTHORS
new file mode 100644
index 0000000..8f95963
--- /dev/null
+++ b/AUTHORS
@@ -0,0 +1,9 @@
+# This the official list of Bazel authors for copyright purposes.
+# This file is distinct from the CONTRIBUTORS files.
+# See the latter for an explanation.
+
+# Names should be added to this file as:
+# Name or Organization <email address>
+# The email address is not required for organizations.
+
+Google Inc.
diff --git a/docs/release.md b/docs/release.md
index ed44457..8dc0c87 100644
--- a/docs/release.md
+++ b/docs/release.md
@@ -18,7 +18,6 @@
3. Identify and set the following environment variables:
* `COMMIT_HASH` the commit hash where the pipeline was run (see below)
- * `JDK_VERSION` the JDK version for which you want to release `java_tools`
* `NEW_VERSION` the new version number you’re trying to release (e.g. `3.1`)
* `RC` the number of the current release candidate
@@ -28,7 +27,6 @@
src/create_java_tools_release.sh \
--commit_hash $COMMIT_HASH \
--java_tools_version $NEW_VERSION \
- --java_version $JDK_VERSION \
--rc $RC --release false
```
@@ -42,7 +40,7 @@
6. Trigger a new build on Downstream https://buildkite.com/bazel/bazel-at-head-plus-downstream.
- Using `pulls/PRNUMBER/head` for the branch.
+ Using `pull/PRNUMBER/head` for the branch.
1. If the CI finishes successfully:
- create the release artifacts from the
@@ -50,7 +48,6 @@
```
src/create_java_tools_release.sh \
--java_tools_version $NEW_VERSION \
- --java_version $JDK_VERSION \
--rc $RC --release true
```
- update the urls of the `http_archive`s in the upgrade PR and send it for
