[Release]: 1.0.2 Service Release

[KyleAure]

Proposal

A couple of issues have been raised via the Jakarta Data mailing list about the TCK.
One a bug, the other an enhancement for a run mode that we had not considered on original development of the TCK.
Let me know if there are any other issues that should be candidates for putting into a service release.

Outstanding work

• TCK: Allow for standalone tests to still go through the deployment process #978
• TCK: EntityTests deployment is missing an entity class #979

Check List

Prepare

• Open this issue.
• Complete outstanding work
• Update TCK Signatures to capture API changes

Stage release

• Update the CHANGELOG.adoc file to reflect the changes put into the new release
• Build and stage artifacts to staging repository
• Build and stage the TCK distribution artifact to download.eclipse.org
• Update this issue with a comment that links to the staged artifacts and the generated GitHub branch and tag
• Create a draft release on GitHub

Verify and modify

• Ask for feedback from the community to verify the staged artifact has all the expected changes.
• If anything needs to be added before publishing do that now and repeat the Stage Release section

Publish release

• Publish staged artifacts to the public repository
• Publish staged TCK distribution artifact to download.eclipse.org
• Update this issue with a comment that links to the published artifacts and the generated GitHub branch and tag
• Modify the draft release on GitHub to be pre-release or latest

Follow up

• Email a Jakarta steering committee member to promote the TCK Distribution publically
• Create pull request to https://github.com/jakartaee/specifications
  • upload generated specification documentation
• Update versions in non-build files, such as:
  Documentation:
  • README.adoc
  • data-tck-reference-guide.adoc