search

jakartaee / platform

The Jakarta EE Platform project produces the Jakarta EE platform specification, which is an umbrella specification that aggregates all other Jakarta EE specifications.
https://jakartaee.github.io/platform/
Eclipse Public License 2.0
200 stars 68 forks source link

Define how the independent release of profiles should work #332

Open starksm64 opened 3 years ago

starksm64 commented 3 years ago

Is your feature request related to a problem? Please describe. We want to be able to release platform specifications on independent release schedules. How should versioning of the platform specifications be done such that this makes sense?

Describe the solution you'd like There should be some major.minor versioning scheme as well as public review releases to increase the pace at which profiles are released and made publicly available.

Describe alternatives you've considered None, this is a new behavior for EE.

Additional context JEP 322: Time-Based Release Versioning

AB#77

kwsutter commented 3 years ago

This issue gets more complicated if we consider releasing a brand new Core Profile before we release the next Platform and Web Profile versions. As we discussed on our Platform call this week... What if Core Profile is released in CY 2021, but the Platform is not released until CY 2022. What version do we name this Core Profile? Core Profile 10 in anticipation of the expected Jakarta EE 10 the following year? Or, maybe some qualification such as 9.next or 10.preview? (I don't necessarily like these, but just trying to get ideas flowing...)

starksm64 commented 3 years ago

Here is a proposal for 5 different versioning schemes: https://docs.google.com/document/d/1ZQGEYSCN5eYtDjWOXAQqNin7iwLKHnQFEP73FDoQdbw/edit?usp=sharing

I believe it is a given that there will be a core profile before the next web and platform specifications are released.

ivargrimstad commented 2 years ago

Still a little left to agree on and document