Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] Summary of the versioning discussion

Based on yesterday's discussion I have added a 5th versioning proposal:

Proposal 5; Match the Java SE 3 Year LTS Timebox for Major with Minor Releases as Appropriate

In this proposal, a major version timebox theme is defined for every 3 years. A goal would be to align with the language features of the latest Java SE LTS release. The timebox date should be offset by a year to allow specifications to fully incorporate the latest Java SE LTS features. The full profile or platform specification would target a single release at the end of the timebox. Profile specifications would produce a M.N release where N starts at 0 and is incremented for each new release as the specification reaches a feature set milestone the specification project deems worthy of a release.

On Tue, May 25, 2021 at 9:42 AM Scott Stark <starksm64@xxxxxxxxx> wrote:

In discussing the Versioning Schemes for Platform & Profile Specifications doc:

A few different topics came up.
1. What is the correct time frame for any time box focus? I think there was a lack of interest in a pure timbebox release notion, but something of a time box of focus. The Java SE LTS model uses a 3 year time frame between LTS releases. I don't think Red Hat has an appetite for less than a 2 year major version timeframe.

2. There should be goals for a given time box of focus for a major release. The EE10 Direction statement:
Outlines several key goals:

* Addressing lack of specification standalone TCKs that can be composed into new platforms
* Defining the makeup of the core profile
* Defining how profile specifications can be released independently and what versioning would look like under this approach
** Introducing release candidates prior to final profile release should be introduced
* Promoting individual specification releases
* Work to define relationship between Jakarta Config and MicroProfile Config
* Updating core profile specifications to enable build time capable implementations
** CDI lite
** Jakarta RESTful Web Services?
* Handling of optional specification features
* Removing the current circularity between specifications at the TCK level
* Java SE version and JPMS strategy
* Improve architecture guidelines and address specification cohesion
** Annotation usage conventions
** Consistent use of CDI

What else should be in focus?

Back to the top