|Re: [jakartaee-platform-dev] Release profiles independently|
That’s why including any MicroProfile technology instead of merging it properly into the Jakarta EE platform first (including Namespace Change) could make that even trickier and more tedious, because a few of these MP features are often buggy and quickly come up with a patch release that a combined TCK would then also have to update for.
So referencing any MP spec would have to be done with great care and very selectively.
Gesendet von Mail für Windows 10
I would suggest that the profile versions align on major/minor versions of the specs they aggregate. When profiles share the same major/minor version of a spec, they have the same 'platform' major/minor. There certainly can be gaps. This would be a possible timeline:
ProfileX has release 10.0 including S1-3.1, S2-5.1, S3-4.0
ProfileX has release 10.1 including S1-3.2, S2-5.1, S3-4.1
Profile Web which extends ProfileX is released with an additional S4-1.0 and is versioned at 10.1.
There still could be Jakarta EE 10 releases that include 10.x revisions of the various profiles if that made sense and was worth the effort. The major issue with actually including all profiles in some timebox that might be triggered by the release of any profile is that work needed to run compatible implementations through the platform/profile TCKs. Just doing this for the sake of having complete releases ala the releases of old does not seem relevant or sustainable.
On Tue, Mar 16, 2021 at 6:44 PM David Blevins <dblevins@xxxxxxxxxxxxx> wrote:
I think the key thing to call out is that this thread has quickly become about simply more profiles, not necessarily releasing them separately. In fact the first responses suggest it be "as part of Jakarta EE 10", which means it's locked in the same release cycle as the Platform and Web Profile. I'm not aware of anyone who has *not* had the idea of more profiles :)
Back to the top