Skip to content

Commit

Permalink
On branch edburns-msft-jea-283-revise-release-plan-gh-platform-820 Ap…
Browse files Browse the repository at this point in the history 
…ply wording from release plan email. (#822)

* On branch edburns-msft-jea-283-revise-release-plan-gh-platform-820 Apply wording from release plan email.
modified:   jakartaee11/JakartaEE11ReleasePlan.md

- See [mail archive](https://www.eclipse.org/lists/jakartaee-platform-dev/msg04374.html).

* On branch edburns-msft-jea-283-revise-release-plan-gh-platform-820 Apply wording from meeting.
modified:   jakartaee11/JakartaEE11ReleasePlan.md

Signed-off-by: Ed Burns <[email protected]>

* On branch edburns-msft-jea-283-revise-release-plan-gh-platform-820 Apply wording from meeting.
modified:   jakartaee11/JakartaEE11ReleasePlan.md

Signed-off-by: Ed Burns <[email protected]>

* On branch edburns-msft-jea-283-revise-release-plan-gh-platform-820 Apply wording from meeting.
modified:   jakartaee11/JakartaEE11ReleasePlan.md

Signed-off-by: Ed Burns <[email protected]>

* On branch edburns-msft-jea-283-revise-release-plan-gh-platform-820 Apply wording from meeting.
modified:   jakartaee11/JakartaEE11ReleasePlan.md

Signed-off-by: Ed Burns <[email protected]>

* On branch edburns-msft-jea-283-revise-release-plan-gh-platform-820 Apply wording from meeting.
modified:   jakartaee11/JakartaEE11ReleasePlan.md

Signed-off-by: Ed Burns <[email protected]>

* On branch edburns-msft-jea-283-revise-release-plan-gh-platform-820 Apply wording from meeting.
modified:   jakartaee11/JakartaEE11ReleasePlan.md

Signed-off-by: Ed Burns <[email protected]>

* On branch edburns-msft-jea-283-revise-release-plan-gh-platform-820 Apply wording from meeting.
modified:   jakartaee11/JakartaEE11ReleasePlan.md

Signed-off-by: Ed Burns <[email protected]>

* On branch edburns-msft-jea-283-revise-release-plan-gh-platform-820 Apply revision in CI source level
modified:   jakartaee11/JakartaEE11ReleasePlan.md

- Thanks @bstansbery

Signed-off-by: Ed Burns <[email protected]>

---------

Signed-off-by: Ed Burns <[email protected]>
Co-authored-by: Ed Burns <[email protected]>
  • Loading branch information
@edburns
edburns and Ed Burns authored Jan 16, 2024
1 parent 9f67fe8 commit 25c1c22
Showing 1 changed file with 22 additions and 14 deletions.
36 changes: 22 additions & 14 deletions jakartaee11/JakartaEE11ReleasePlan.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -10,23 +10,24 @@
| *Platform* | | | Plan Review | | | | |
| *All* | | | | TCK pass w/Security Manager Disabled | | | |
| *All* | | | | M1 release | | | |
| *All* | | | | | Wave 1, 2, 3, 4 specs release review by 2024-01-30 | | |
| *All* | | | | | Wave 1, 2, 3, 4 specs release review initiated by 2024-02-29 | | |
| *All* | | | | | M2 release | | |
| *All* | | | | | Wave 5 specs release review by 2024-02-29 | | |
| *All* | | | | | Wave 5 specs release review initiated by 2024-03-29 | | |
| *All* | | | | | M3 release | | |
| *All* | | | | | Wave 6, 7 specs release review by 2024-03-29 | | |
| *All* | | | | | M4 release | | |
| *All* | | | | | TCK pass on Java SE 21 | | |
| *Components* | | | | | Individual Component Spec Ballots | | |
| *Platform* | | | | | Platform TCK pass on Java SE 21 | | |
| *Components* | | | | | | Complete implementations | |
| *Components* | | | | | Each Wave 1 - 5 component spec has an impl that passes its TCK on Java SE 17 and an impl that passes its TCK on Java SE 21. These need not be the same impl. | | |
| *Components* | | | | | | Each Wave 6, 7 component spec has an impl that passes its TCK on Java SE 17 and an impl that passes its TCK on Java SE 21. These need not be the same impl. | |
| *All* | | | | | | Wave 6, 7 specs release review initiated by 2024-04-27 | |
| *All* | | | | | | M4 release | |
| *Components* | | | | | | Individual component spec ballots completed | |
| *Platform* | | | | | | Platform TCK ready to run on Java SE 21 and Java SE 17 | |
| *Components* | | | | | | Further refine implementations | |
| *Platform* | | | | | | | Platform ballot |
| *Platform* | | | | | | | Web Platform ballot |
| *Platform* | | | | | | | Core Platform ballot |
| *Platform* | | | | | | | **Release** |

For all milestone releases after M1:
* specs that are slated to have release review before that milestone will include their final versions in the milestone.
* specs that are slated to have release review initiated before that milestone will include their final versions in the milestone.
* all other specs will include the latest version they have on hand. (Ed and Arjan commit to do the release work for this case, if necessary.)

## Scope ([issue]())
Expand All @@ -48,20 +49,27 @@ Continue to make CDI the single component model used across all of EE by removin

With the help of the platform project, the CDI project will do the work to move all aspects of CDI that deal with integrating CDI with other specifications out of the CDI spec and into the platform spec or appropriate profile spec. The remaining content will still be called CDI. For more information see the [CDI issue tracker](https://github.com/jakartaee/cdi/issues/687#issuecomment-1667009015).

### API Source and Target Level
If a component Specification is planning a Major or Minor version update for Jakarta EE 11, then the recommendation would be to recompile and distribute the specification’s APIs at lowest required of Java SE 17 and Java SE 21.
### API Source Code `--release` Level

**Note:** A component specification may be required to recompile to a higher Java SE level than it actually use depending on the specifications it depends on.
For the Jakarta EE Platform (Platform, Web and Core), the Java compiler `--release` option is 17. For the component specs, the Jakarta EE Platform requires the Java compiler `--release` option is **at most** 17, but component specifications can decide on a lower level.

### TCK Source Level
The TCK for specifications updated in EE 11 will be compiled at the Java SE 21 level.

- Component spec TCKs and platform TCK must compile at Java 17 or less.
- A compatible component impl must pass their component TCK when run under Java 17 or 21.
- To ratify a component specification, there must exist an implementation that passes on Java 17. There must also exist an implementation that passes on 21.
- These need not be the same implementation. There can be one implementation that passes on 17 and a different one that passes on 21.
- A compatible platform impl must pass the platform TCK when run under 17 or 21.
- To ratify a platform specification, there must exist an implementation that passes on 17. There must also exist an implementation that passes on 21.
- These need not be the same implementation. There can be one implementation that passes on 17 and a different one that passes on 21.

#### Signature Tests
In Jakarta EE 9.1, the framework for performing API Signature tests was updated to make it easier to test Signatures across multiple Java levels.
The framework and/or API tests may need to be tweaked as we continue to learn and experiment with future levels of Java.

### Compatible Implementation (CI) Source Level
How a Compatible Implementation supports the Java SE 21 runtime (or above) will be left as a vendor-defined solution.

The long-standing policy of considering specification API binaries, in Maven Central or anywhere else, as a non-normative convenience remains unchanged. The platform project is silent on this matter. However, because the platform project does mandate a specific JDK requirement for compatible implementations passing the component or platform TCK, if a component specification does publish an API binary, that binary is practically constrained to follow that mandate." See [TCK Source Level](#tck-source-level)

## JPMS Module Info classes ([issue](https://github.com/eclipse-ee4j/jakartaee-platform/issues/329))
Suggestions on support for JPMS modules were introduced in the Jakarta EE 9 Platform Specification.
Expand Down

0 comments on commit 25c1c22

Please sign in to comment.