I'd like to extend Ivar's answer by one point: Specs can publish many releases within the lifetime of one Jakarta EE release, hence their pushing is always unrelated of Jakarta EE and typically should be done *long before* Jakarta EE is iteself starting its ballot. In fact, what people "out there" expect is that the ballot for Jakarta EE is basing on already published specs, not basing on Milestones or Candidates. Looking on Jakarta EE from that point makes it clear that EE 8 and EE 9 enforced unneccessary and unwanted waiting, and we should never again without anything that successfully passed a ballot. These are not chapters of a book, these are standalone documents.
-Markus
Von: jakartaee-platform-dev-bounces@xxxxxxxxxxx [mailto:jakartaee-platform-dev-bounces@xxxxxxxxxxx] Im Auftrag von Steve Millidge (Payara)
Gesendet: Donnerstag, 19. November 2020 10:18
An: jakartaee-platform developer discussions
Betreff: Re: [jakartaee-platform-dev] Releasing api jars to central
Thanks I will get the checklist steps done now then
From: jakartaee-platform-dev-bounces@xxxxxxxxxxx <jakartaee-platform-dev-bounces@xxxxxxxxxxx> On Behalf Of Ivar Grimstad
Sent: 18 November 2020 18:28
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: Re: [jakartaee-platform-dev] Releasing api jars to central
Hi Steve,
That is part of the competition steps for the specification project team after their ballot is passed. Should be done for each component specification as soon as possible after the ballot completes.
--
Ivar Grimstad
Jakarta EE Developer Advocate | Eclipse Foundation, Inc.
Eclipse Foundation - Community. Code. Collaboration.