[Release]: Milestone 1.0.0-M3

[KyleAure]

Proposal

There have been additional changes to the API and TCK that will require an additional milestone release.

Outstanding work

• allow Delete with no parameters to make BasicRepository.deleteAll() valid #413
• [Fix]Should non-standard query by methods be supported by user defined repositories #414
• Fix TCK test errors #411
• At Update annotation, should we be most restrict #410
• reintroduce static metamodel? #394
• TCK allow certification against Java 17 and 21 #421
• Sort with type parameter #432

Anything else we need to go into Milestone 3?

Check List

Prepare

• Open this issue.
• Complete outstanding work
• (Update TCK Signatures to capture API changes)[https://github.com/jakartaee/data/actions/workflows/release.yml]

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 pre-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 pre-release on GitHub to be latest

Follow up

• Email a Jakarta steering committee member to promote the TCK Distribution publically
• Update versions in non-build files, such as:
  Documentation:
  • README.adoc
  • data-tck-reference-guide.adoc

[njr-11]

Excellent idea to create a Milestone 3 given the updates! We should have a final answer regarding the last issue in the list, #394, on Wednesday, Jan 17 if everyone attends the Jakarta Data meeting that day.

[KyleAure]

Milestone 3 is staged:

• GitHub Tag: 1.0.0-M3
• GitHub Branch: RELEASE-1.0.0-M3
• GitHub Prerelease: 1.0.0-M3
• Staging repo: jakartadata-1016

@njr-11 @otaviojava I know there was some more refinement needed for the static metamodel based on the comments on #394. Let me know if you think any of that should go into milestone 3, otherwise, I can go ahead and publish it.

Status:

• Need to rebuild staged due to Missing Sort in TCK test #433
• Still waiting for the outcome of Sort with type parameter #432

[KyleAure]

Milestone 3 is re-staged:

• GitHub Tag: 1.0.0-M3
• GitHub Branch: RELEASE-1.0.0-M3
• GitHub Prerelease: 1.0.0-M3
• Staging repo: jakartadata-1017

FYI - @njr-11 @otaviojava let me know if this looks good and I go ahead and publish the release.

[lprimak]

Please use "Release Drafts" to indicate that the release is not public. Currently, it looks like M3 is released on GitHub but it's not in Maven Central.

Thank you!

[KyleAure]

@lprimak I marked 1.0.0-M3 as pre-release I figured that would indicate it hasn't been released yet. Perhaps I misunderstood what the use case of pre-release would be.

[lprimak]

Either you or me :)
I always thought that pre-release was alpha, beta, etc. and it's all "deployed" in central but not considered a "final" release.

[KyleAure]

Ahh. I can change this process to use drafts instead. I assume you get a notification if I mark it pre-release?

[lprimak]

Thanks Kyle!
Yes, I got a notification and assumed that it was (or would shortly be) on Maven Central.
I also updated Jakarta EE platform to use it.
Is M3 going to be released soon or would I need to revert the Jakarta EE platform change to use M2 instead?
If M3 going to be released soon, I will just leave it alone as Platform M2 isn't scheduled for another few weeks I think

[KyleAure]

I believe there is just one more doc change that needs to go in and then I'll go forward with a stage/release.

[gavinking]

@KyleAure I don't think #474 should block the release. We have not reached consensus on it.

[KyleAure]

Milestone 3 is re-staged:

• GitHub Tag: 1.0.0-M3
• GitHub Branch: RELEASE-1.0.0-M3
• GitHub Release (DRAFT): 1.0.0-M3
• Staging repo: jakartadata-1018

FYI - @gavinking @otaviojava @njr-11 @lprimak I'll test this against Open Liberty tomorrow and push to maven central so long as there are no other changes y'all want to be put in (that can't wait for M4)

[KyleAure]

Milestone 3 is released 🚀 :

• GitHub Tag: 1.0.0-M3
• GitHub Branch: RELEASE-1.0.0-M3
• GitHub Release (pre-release): 1.0.0-M3
• Maven Central: jakarta.data-api

[gavinking]

Nice!

And now that it's available, I have already made an excellent start on an implementation!

hibernate/hibernate-orm#7888

The main challenge is going to be the keyset-based pagination stuff.