I may be being a bit dumb but why do specs need to wait to be approved based on the availability of downstream specs being approved given that at this point in time nothing is changing and most specs
are boilerplate? Surely as long as all other api artifacts are staged and therefore the correct version be referenced in the pom dependencies for the api jar then we can proceed? I’m sure I am missing something here.
Steve
From: jakarta.ee-spec.committee-bounces@xxxxxxxxxxx <jakarta.ee-spec.committee-bounces@xxxxxxxxxxx>
On Behalf Of Kevin Sutter
Sent: 06 August 2019 22:32
To: Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Subject: [jakarta.ee-spec.committee] Plan B Deliverable for JakartaOne and OC1?
Hi,
I know we're all busy trying to be ready by JakartaOne and OC1. I believe that we have to announce *something* significant at JakartaOne and/or OC1, or we will have another nail in our Jakarta EE
coffin... So, what's our Plan B?
What about if we would limit our focus to just Jakarta EE 8 Web Profile? That would significantly decrease the number of required Specifications and associated artifacts to review. Consider all
of the PRs, Specs, APIs, Javadocs, CIs, TCKs, Certification Requests, and I'm probably forgetting something... And, we would still be delivering a usable subset of functionality. With the goal of delivering the rest of Jakarta EE by EclipseCon Europe (one
month later).
Think about it. We can talk about tomorrow.
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
