| Re: [jakartaee-platform-dev] Release review progress of Jakarta EE 10 platform Full Profile |
FWIW, from a marketing communication perspective we would almost
certainly only do a single press release and PR/AR push. So from a
communications PoV there is little value in releasing the profiles
independently.
I don't mean to imply that this is that big of a deal, but wanted
to provide an additional datapoint to the discussion.
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.ThanksEmily
On Mon, Jul 18, 2022 at 10:47 PM Ondro Mihályi <mihalyi@xxxxxxxxxxx> wrote:
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.
Ondro
_______________________________________________On Mon, Jul 18, 2022, 21:53 Scott Stark <starksm64@xxxxxxxxx> wrote:
_______________________________________________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.
On Jul 18, 2022 at 2:23:52 PM, Ondro Mihályi <mihalyi@xxxxxxxxxxx> wrote:
Hi,
Since, GlassFish now passes the EE 10 Full Profile TCK, I believe that we can proceed with the release review. The PR is already created here: https://github.com/jakartaee/specifications/pull/498
There are a few outstanding things to do that I know of:
- The spec documents (PDF and HTML) have status "DRAFT" -they need to be regenerated with the status FINAL
- The release record should be updated: https://projects.eclipse.org/projects/ee4j.jakartaee-platform/releases/10 - it still mentions March 31, 2022
- IP Log should be generated
- email PMC and EMO so that the ballot can start
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?
All the best,,Ondro Mihalyi
Director, Jakarta EE expert
OmniFish - Jakarta EE Consulting & Support | www.omnifish.ee
Omnifish OÜ, Narva mnt 5, 10117 Tallinn, Estonia | VAT: EE102487932_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
--
Thanks
Emily
_______________________________________________ jakartaee-platform-dev mailing list jakartaee-platform-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
Mike Milinkovich
Executive Director | Eclipse Foundation AISBL
Twitter:@mmilinkov