I disagree on the view that the
Platform Profiles are independent - strongly!
From the users perspective I would
expect that I can switch between the Platform aka Full Profile to
the Web Profile of the same Version without change in behaviour of
the underlying implementations, which is ensured by the
corresponding component specs.
The Web Profile is a direct
sub-component of the Full Profile/Platform - without a final Web
Profile version there can not exist a Full Profile/Platform final
release!
This is a little bit different
regarding the Core Profile to Web Profile relation, as this is
more lose coupled - but even this has no different view from the
users perspective.
Releasing Jakarta 10 Platform/Full
Profile final release now without a final version the Web Profile
can result in a requirement for the user to switch from 10.0.0 Web
Profile to 10.0.1 Full Profile (or even worse version mismatch) to
get the same component spec versions in the application platform
implementation - do we really put that burden on the users to do a
mapping of versions of a Platform/Profile Release?
On my opinion this as worse as having
different related versions on the spec document, API and TCK for
the same specification - these are different, but strong coupled,
dimensions of the same thing. But I know the majority of the
Committee might disagree on that (currently) ;-)
The Platform Profiles are coupled via
it´s contents and versions - and this is an expected behaviour and
a good thing in this case.
So I think, we should concentrate
efforts on fixing the remaining things for the 10.0.0 release and
then release them together instead of separating the current
Platform project into separate platforms.
Best,
Jan
Am 19.07.22 um 11:40 schrieb Emily
Jiang via jakartaee-platform-dev:
I also think these three releases (platform, web and core
profile) should be independent. We can start the Jakarta EE 10
platform release ballot since it is ready. I do agree that we
need to make the ballot very explicit.
I agree that this should be discussed at the
platform call. But I believe that Web and Core profiles
shouldn't block releasing the Full profile. Jakarta EE 10
has been delayed already for a long time and it'sbetter to
release the Full profile alone rather than wait for Web and
Core profiles to release everything together.
I'll update the specs to final and
update the PR after tomorrow's platform call to make
sure there are no outstanding issues and then I can
complete the other tasks. The only concern I have
about the platform ballot is the changes needed for
the concurrency tck of the web profile. We need to be
clear what we are doing to resolve this, so it will be
a topic for tomorrow's platform call.
Can somebody from the platform cmmitters
have a look if they can do any of the above
and check whether something else must be done
before going to the ballot?
We need Scott who originally raised the
specification PR to update the PR and move it
out of the draft mode. If Scott isn't around
(he might be on holiday these days), can
somebody else raise a new PR so that we can
get all things ready for a ballot?
