jakartaee / jakartaee/jsonb-api
[Release]: 3.1.0-M2
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 95
- Forks
- 41
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 35
Description
Proposal
Milestone 1 was released almost 4 months ago.
Let's do a Milestone 2 release to get the current state of the project out there.
Then a Release Candidate before GA.
I know not much has gone into the Jakarta JSON Bind spec this go around, but I think for EE 13 we can do a major release and fix more of the fundamental bugs/issues in this specification.
Outstanding work
Check List
Prepare
- Open this issue.
- Complete outstanding work
- Update TCK Signatures to capture API changes
Stage release
- Build and stage artifacts to staging repository
- Pull 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
draftrelease 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 Releasesection
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
draftrelease on GitHub to bepre-releaseorlatest
Follow up
- Email a Jakarta steering committee member to promote the TCK Distribution publically
- Create pull request to https://github.com/jakartaee/specifications
- Update versions in non-build files, such as:
Documentation:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the outstanding pull request 453 and issue 63, then follow the Prepare, Stage release, Verify and modify, Publish release, and Follow up checklist. Use the linked CI jobs and the update.yml and specification.yml workflows; done means staged artifacts are verified and published, the GitHub release and generated branch/tag are updated, and README.adoc versions are current.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100