[Release]: 1.1.0-M3

[KyleAure]

Proposal

We should look at releasing an M3 by the end of March.
Let me know if there are any other issues/PRs we want to include in an M3.

Outstanding work

• [Bug]: Problems in M2 #1364
• TCK: Fix read-only tests #1397
• Avoid ambiguity in dataStore name requirements #1406
• Switch back to java 17 build #1410

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

[dstepanov]

I want to try changes related to #1290

[KyleAure]

We are targeting M3 for release by the end of March. Stay tuned 👀

[KyleAure]

@otaviojava @njr-11
I didn't take very good personal notes during our meeting last week.
Are we waiting for #1406 before doing a M3 release or are we good with what we have in now?

[njr-11]

@otaviojava @njr-11 I didn't take very good personal notes during our meeting last week. Are we waiting for #1406 before doing a M3 release or are we good with what we have in now?

It's only a Javadoc clarification. I wouldn't hold up a milestone over it.

[KyleAure]

Issues staging M3. See ticket: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/7344

[KyleAure]

@dstepanov 1.1.0-M3 has been staged, wanna give it a try?

Staged release: https://repo.eclipse.org/#browse/browse:data-maven2-staging:jakarta%2Fdata%2Fjakarta.data-api%2F1.1.0-M3
GitHub draft: https://github.com/jakartaee/data/releases/edit/untagged-e153ee0fa17c984abc61

[KyleAure]

Published release: https://repo1.maven.org/maven2/jakarta/data/jakarta.data-api/1.1.0-M3/
Github release: https://github.com/jakartaee/data/releases/tag/1.1.0-M3