[0.8.0] Create the release branch and initial tag

[DanHeidinga]

https://github.com/eclipse/openj9/blob/master/doc/processes/release_process.md

• Pick candidate level based on Adopt builds
  OpenJ9 CI build: https://ci.eclipse.org/openj9/view/Pipelines/job/Pipeline-Build-Test-JDK8-linux_ppc-64_cmprssptrs_le/89/

OpenJ9: c613ef1
OMR: 3898c5e
OpenJDK: 789de43

Adopt CI build: https://ci.adoptopenjdk.net/job/openjdk8_openj9_build_ppc64le_linux/80/

openj9 453326f7ac50eba1039d35b10498263990eeae1a
omr: 1f7d88e0acbe93345388a7768faa425a14efeee9

Using the OpenJ9 CI levels as the adopt builds appear to be building from the branch created to test the release process.

Branch name: v0.8.0-release
Tag: openj9-0.8.0-rc1
RC-1 shas:

OpenJ9: c613ef1
OMR: 3898c5e

• JDK8 extensions repo update to pull the rc1 tag
  Update OpenJ9 and OMR levels ibmruntimes/openj9-openjdk-jdk8#51

Tag: openj9-0.8.0-rc2
RC-2 shas:

OpenJ9: e24e8aa
OMR: 3e8296b

Tag: openj9-0.8.0
Final shas: (same as -rc2)

OpenJ9: e24e8aa
OMR: 3e8296b

• JDK8 extensions repo update to pull the rc2 tag
  Get sources from openj9-0.8.0-rc2 tag for OpenJ9 and OMR ibmruntimes/openj9-openjdk-jdk8#56

• Adopt Slack discussion on enabling JDK 8 Extensions release builds:
  https://adoptopenjdk.slack.com/archives/C09NW3L2J/p1519747803000254

• AdoptOpenJDK test plan / status: Confirm test plan executed against openjdk8-openj9 release 0.8 candidate build adoptium/aqa-tests#309

[DanHeidinga]

openj9

$ git branch v0.8.0-release c613ef1
$ git checkout v0.8.0-release
$ git tag -a openj9-0.8.0-rc1
$ git push origin v0.8.0-release --follow-tags

openj9-omr

$ git branch v0.8.0-release 3898c5e
$ git checkout v0.8.0-release
$ git tag -a openj9-0.8.0-rc1
$ git push origin v0.8.0-release --follow-tags

Message for the annotated tag:

Eclipse OpenJ9 v0.8.0 Release Candidate 1

Repo SHAs
OpenJ9: c613ef1
OMR: 3898c5e

[DanHeidinga]

@andrew-m-leonard FYI - Please update the Extensions repo to use this branch and tag for the 0.8.0 release. Thanks

[DanHeidinga]

Tested the build with:

bash get_source.sh -openj9-branch=v0.8.0-release -openj9-sha=openj9-0.8.0-rc1 -omr-branch=v0.8.0-release  -omr-sha=openj9-0.8.0-rc1

resulting in the following java -version output:

# ./build/linux-x86_64-normal-server-release/images/j2sdk-image/bin/java -version
openjdk version "1.8.0_162-internal"
OpenJDK Runtime Environment (build 1.8.0_162-internal-_2018_02_26_19_59-b00)
Eclipse OpenJ9 VM (build openj9-0.8.0-rc1, JRE 1.8.0 Linux amd64-64 Compressed References 20180226_000000 (JIT enabled, AOT enabled)
OpenJ9   - c613ef1
OMR      - 3898c5e
JCL      - 789de43 based on jdk8u162-b12)

[DanHeidinga]

Remaining fixes are in. Tagging last night's build as -rc2

SHAs:

OpenJ9: e24e8aa
OMR: 3e8296b
OpenJDK: 6d7d67e

Message for the annotated tag:

Eclipse OpenJ9 v0.8.0 Release Candidate 2

Repo SHAs
OpenJ9: e24e8aa
OMR: 3e8296b

[DanHeidinga]

-rc2 build being used by Adopt for testing: https://ci.adoptopenjdk.net/job/openjdk8_openj9_build_x86-64_linux/112/artifact/OpenJDK8_x64_Linux_201806031733.tar.gz

[DanHeidinga]

AdoptOpenJDK test plan: adoptium/aqa-tests#309

[DanHeidinga]

See ibmruntimes/openj9-openjdk-jdk8#63 for the PR to update to the final tag.

That can be merged once we've tagged our repos with the final tag.

[DanHeidinga]

Tagged the repo for the final build as testing at Adopt has completed on x86.
Adopt has run automated JCKs on x,p,390 and manual tests on x.

Commands for the tag:

git tag -a openj9-0.8.0
git push origin v0.8.0-release --follow-tags

Message for the tag:

Eclipse OpenJ9 v0.8.0

Repo SHAs
OpenJ9: e24e8aa
OMR: 3e8296b

[DanHeidinga]

Remaining steps for this release:

• Create the github release corresponding to the tagged level. The release should link to the Eclipse Release document, the release issue, and the AdoptOpenJDK download links.
  https://github.com/eclipse/openj9/releases/tag/openj9-0.8.0
• Open an Eclipse Bugzilla requesting the branch be marked protected to prevent commits after the release is complete.
• Remove the doc:releasenote tag from items that were included in the release notes.
  The 7 items still tagged as releasenotes will apply to any release until they are addressed.

[DanHeidinga]

Link to the bug to protect the branch: https://bugs.eclipse.org/bugs/show_bug.cgi?id=533227