Re: [jsonb-dev] [jakartaee/jsonb-api] Create Release Plan for JSON Bindi

[Nathan Rauh <nathan.rauh@xxxxxxxxxx>]

I haven’t seen any discussion in response to Jared’s email/issue, but given that some work has already been completed in the jsonb-api repository, I assume we will be aiming for a release of JSON Binding for Jakarta EE 12.

 

The deadline for specification release plans is approaching, so following the approach used by some other Jakarta EE spec that I’ve worked on and which already have release plans or proposed release plans, I created a 3.1 Milestone where issues can be placed that we would like to include.  To start with, it includes the issues which were already completed (the PR for Java record support and a few minor fixes).  Over the next week, could everyone add the other issues that should be targeted to a 3.1 release?  If anyone doesn’t have permission, please ask on the list and one of us with permission can assign the issue’s Milestone to 3.1.  Assuming there is agreement, a release plan can be created from the Milestone as was done for other specs.

 

From: Jared Anderson <notifications@xxxxxxxxxx>
Date: Monday, February 24, 2025 at 5:49 PM
To: jakartaee/jsonb-api <jsonb-api@xxxxxxxxxxxxxxxxxx>
Cc: Subscribed <subscribed@xxxxxxxxxxxxxxxxxx>
Subject: [EXTERNAL] [jakartaee/jsonb-api] Create Release Plan for JSON Binding for Jakarta EE 12 (Issue #367)

Follow the release plan process in the Jakarta Specification process guide to create a release plan for Jakarta JSON Binding for inclusion in Jakarta EE 12. Link to release plan for your component: https: //projects. eclipse. org/projects/[component]/releases/[x. y]/plan

Follow the release plan process in the Jakarta Specification process guide to create a release plan for Jakarta JSON Binding for inclusion in Jakarta EE 12.

• Link to release plan for your component: https://projects.eclipse.org/projects/[component]/releases/[x.y]/plan
• Link to release plan review PR in the specifications repository: https://github.com/jakartaee/specifications/pull/xxx

Things to include in the release plan are (but not limited to):

• New features
• Deprecation of existing function (which may be replaced with new function)
• Removal of previously deprecated function (requires a major version update)
• Other backward incompatible changes besides removal of deprecated function (requires major version update)
• Added or removed dependencies
• Notable newer Java SE features used
• New TCK tests for existing function that was not tested enough or tested at all
• Moving TCK from platform TCK to platform-tck repository to component repository
• Minimum Java SE version update (For Jakarta EE 12, the platform committee has declared that Java SE 21 will be the minimum Java SE level. As such I believe most release plans should state the same minimum Java SE level of 21.)

For each item in your release plan, there should be an issue opened in your repository and it should have the label EE12.

Resources to review for ideas of what to include in your release plan are this GitHub query that includes Jakarta platform issues that are labeled EE12, this google doc that is tracking ideas for Jakarta EE 12 content, and existing issues in your component's GitHub repository.

If your component does not plan to have a new release for inclusion in Jakarta EE 12 and just plans to use an existing release, close out this issue with that information. Do note that if your component is referenced in jakartaee/platform#1018, you should be planning to have a minor release at minimum. It may only contain the changes to remove references to SecurityManager / AccessController.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <jakartaee/jsonb-api/issues/367@xxxxxxxxxx>

jhanders34 created an issue (jakartaee/jsonb-api#367)

Follow the release plan process in the Jakarta Specification process guide to create a release plan for Jakarta JSON Binding for inclusion in Jakarta EE 12.

• Link to release plan for your component: https://projects.eclipse.org/projects/[component]/releases/[x.y]/plan
• Link to release plan review PR in the specifications repository: https://github.com/jakartaee/specifications/pull/xxx

Things to include in the release plan are (but not limited to):

• New features
• Deprecation of existing function (which may be replaced with new function)
• Removal of previously deprecated function (requires a major version update)
• Other backward incompatible changes besides removal of deprecated function (requires major version update)
• Added or removed dependencies
• Notable newer Java SE features used
• New TCK tests for existing function that was not tested enough or tested at all
• Moving TCK from platform TCK to platform-tck repository to component repository
• Minimum Java SE version update (For Jakarta EE 12, the platform committee has declared that Java SE 21 will be the minimum Java SE level. As such I believe most release plans should state the same minimum Java SE level of 21.)

For each item in your release plan, there should be an issue opened in your repository and it should have the label EE12.

Resources to review for ideas of what to include in your release plan are this GitHub query that includes Jakarta platform issues that are labeled EE12, this google doc that is tracking ideas for Jakarta EE 12 content, and existing issues in your component's GitHub repository.

If your component does not plan to have a new release for inclusion in Jakarta EE 12 and just plans to use an existing release, close out this issue with that information. Do note that if your component is referenced in jakartaee/platform#1018, you should be planning to have a minor release at minimum. It may only contain the changes to remove references to SecurityManager / AccessController.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <jakartaee/jsonb-api/issues/367@xxxxxxxxxx>