Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] Release profiles independently

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 :)

Responding on the topic of profiles actually being separate released, the main thing we'd have to be aware of is we'd no longer be able to say "Jakarta EE 10", or "Jakarta EE 11".  Those days would be over.  We'd instead have "Jakarta EE Platform 10.2, Jakarta EE WebProfile 11 and Jakarta EE Cloud Profile 14 have been released!"

Anyone have any thoughts on that?


jakartaee-platform-dev mailing list
To unsubscribe from this list, visit

Back to the top