Skip to content

Commit

Permalink
Releasing.md updates (banner and release notes) (#1669)
Browse files Browse the repository at this point in the history 
* Adjust AIX RAM limit down to aid JDK14 (#1555)

Signed-off-by: Stewart Addison <[email protected]>

* doc: Add banner and release note info to RELEASING.md

Signed-off-by: Stewart Addison <[email protected]>

Co-authored-by: Stewart X Addison <[email protected]>
  • Loading branch information
@sxa @sxa555
sxa and sxa555 authored Apr 15, 2020
1 parent 86edc5b commit 9cb69ec
Showing 1 changed file with 12 additions and 12 deletions.
24 changes: 12 additions & 12 deletions RELEASING.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,6 @@ Don't be scared off by this document! If you already understand the stuff in th
- Regular builds are tagged every week or so in a format such as `jdk-13+21`
- Eventually after rampdown and final phase testing the GA build is tagged and released, e.g. the `jdk-13-ga` code level is tagged along side the actual release build tag.


### OpenJDK Vulnerability Group

- A private group of trusted people who take reports of vulnerabilities in the openjdk codebase and work to resolve them and get them into releases in a timely manner
Expand Down Expand Up @@ -103,7 +102,8 @@ Don't be scared off by this document! If you already understand the stuff in th

Here are the steps:

1. Build and Test the OpenJDK for "release" at AdoptOpenJDK using a build pipeline job as follows:
1. If desired, add a banner to the website to indicate that the releases are coming in the near future ([Sample PR](https://github.com/AdoptOpenJDK/openjdk-website/pull/702/files))
2. Build and Test the OpenJDK for "release" at AdoptOpenJDK using a build pipeline job as follows:
* Job: https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk8-pipeline/build (Switch `openjdk8` for your version number)
* `targetConfigurations`: remove all the entries for the variants you don't want to build (e.g. remove the openj9 ones for hotspot releases) or any platforms you don't want to release (Currently that would include OpenJ9 aarch64)
* `releaseType: Release`
Expand All @@ -117,29 +117,29 @@ Here are the steps:
* For OpenJ9 (all versions) use the OpenJ9 branch e.g. `openj9-0.15.1`
* `enableTests`: tick
* SUBMIT!!
2. Once the Build and Test pipeline has completed,
3. Once the Build and Test pipeline has completed,
[triage the results](https://github.com/AdoptOpenJDK/openjdk-tests/blob/master/doc/Triage.md)
([TRSS](https://trss.adoptopenjdk.net/tests/Test) will probably help!)
* Find the milestone build row, and click the "Grid" link
* Check all tests are "Green", and if not "hover" over the icon and follow the Jenkins link to triage the errors...
* Raise issues either at:
* [openjdk-build](https://github.com/adoptopenjdk/openjdk-build) or [openjdk-tests](https://github.com/AdoptOpenJDK/openjdk-tests) (for Adopt build or test issues)
* [eclipse/openj9](https://github.com/eclipse/openj9) (for OpenJ9 issues)
3. Discuss failing tests with [Shelley Lambert](https://github.com/smlambert)
4. If "good to publish", then get permission to publish the release from the Adopt TSC members, discussion is via the AdoptOpenJDK [#release](https://adoptopenjdk.slack.com/messages/CLCFNV2JG) Slack channel and create a Promotion TSC item [here](https://github.com/AdoptOpenJDK/TSC/issues/new?assignees=&labels=&template=promote-release.md&title=Promote+AdoptOpenJDK+Version+%3Cx%3E).
5. Once permission has been obtained, run the [Adopt "Publish" job](https://ci.adoptopenjdk.net/job/build-scripts/job/release/job/refactor_openjdk_release_tool/) (restricted access - if you can't see this link, you don't have access)
4. Discuss failing tests with [Shelley Lambert](https://github.com/smlambert)
5. If "good to publish", then get permission to publish the release from the Adopt TSC members, discussion is via the AdoptOpenJDK [#release](https://adoptopenjdk.slack.com/messages/CLCFNV2JG) Slack channel and create a Promotion TSC item [here](https://github.com/AdoptOpenJDK/TSC/issues/new?assignees=&labels=&template=promote-release.md&title=Promote+AdoptOpenJDK+Version+%3Cx%3E).
6. Once permission has been obtained, run the [Adopt "Publish" job](https://ci.adoptopenjdk.net/job/build-scripts/job/release/job/refactor_openjdk_release_tool/) (restricted access - if you can't see this link, you don't have access)
* `TAG`: (github binaries published name)  e.g. `jdk-11.0.5+9` or `jdk-11.0.5+9_openj9-0.nn.0` for OpenJ9 releases. If doing a point release, add that into the name e.g. for a `.3` release use something like these (NOTE that for OpenJ9 the point number goes before the openj9 version): `jdk8u232-b09.3` or `jdk-11.0.4+11.3_openj9-0.15.1`
* `VERSION`: (select version)
* `UPSTREAM_JOB_NAME`: (build-scripts/openjdkNN-pipeline)
* `UPSTREAM_JOB_NUMBER`: (the job number of the build pipeline under build-scripts/openjdkNN-pipeline) eg.86
* `RELEASE`: "ticked"
* SUBMIT!!
6. Once the job completes successfully, check the binaries have uploaded to github at somewhere like https://github.com/AdoptOpenJDK/openjdk8-binaries/releases/jdk8u232-b09
7. Within 15 minutes the binaries should be available on the website too at e.g. https://adoptopenjdk.net/?variant=openjdk11&jvmVariant=openj9
8. Since you have 15 minutes free, use that time to update https://github.com/AdoptOpenJDK/openjdk-website/blob/master/src/handlebars/support.handlebars which is the source of https://adoptopenjdk.net/support.html and (if required) the supported platforms table at https://github.com/AdoptOpenJDK/openjdk-website/blob/master/src/handlebars/supported_platforms.handlebars which is the source of https://adoptopenjdk.net/supported_platforms.html.
9. [Mac only] Once the binaries are available on the website you need to run the [homebrew-cask_updater](https://ci.adoptopenjdk.net/job/homebrew-cask_updater/) which will create a series of pull requests [here](https://github.com/AdoptOpenJDK/homebrew-openjdk/pulls). Normally George approves these but in principle as long as the CI passes, they should be good to approve. You don't need to wait around and merge the PR's because the Mergify bot will automatically do this for you as long as somebody has approved it.
10. Publicise the Adopt JDK release via slack on AdoptOpenJDK #release
11. If desired, find someone with the appropriate authority (George, Martijn, Shelley, Stewart) to post a tweet about the new release from the AdoptOpenJDK twitter account
7. Once the job completes successfully, check the binaries have uploaded to github at somewhere like https://github.com/AdoptOpenJDK/openjdk8-binaries/releases/jdk8u232-b09
8. Within 15 minutes the binaries should be available on the website too at e.g. https://adoptopenjdk.net/?variant=openjdk11&jvmVariant=openj9
9. Since you have 15 minutes free, use that time to update https://github.com/AdoptOpenJDK/openjdk-website/blob/master/src/handlebars/support.handlebars which is the source of https://adoptopenjdk.net/support.html and (if required) the supported platforms table at https://github.com/AdoptOpenJDK/openjdk-website/blob/master/src/handlebars/supported_platforms.handlebars which is the source of https://adoptopenjdk.net/supported_platforms.html, and also update https://adoptopenjdk.net/release_notes.html ([Sample change](https://github.com/AdoptOpenJDK/openjdk-website/pull/675/commits/563d8e2f0d9d26500a7e8d9eca61b491f73f1f37)
10. [Mac only] Once the binaries are available on the website you need to run the [homebrew-cask_updater](https://ci.adoptopenjdk.net/job/homebrew-cask_updater/) which will create a series of pull requests [here](https://github.com/AdoptOpenJDK/homebrew-openjdk/pulls). Normally George approves these but in principle as long as the CI passes, they should be good to approve. You don't need to wait around and merge the PR's because the Mergify bot will automatically do this for you as long as somebody has approved it.
11. Publicise the Adopt JDK release via slack on AdoptOpenJDK #release
12. If desired, find someone with the appropriate authority (George, Martijn, Shelley, Stewart) to post a tweet about the new release from the AdoptOpenJDK twitter account

# [OpenJ9 Only] Milestone Process

Expand Down

0 comments on commit 9cb69ec

Please sign in to comment.