[jakartaee-platform-dev] Release Candidate APIs vs Milestone APIs

["Kevin Sutter" <sutter@xxxxxxxxxx>]

Hi,
I've been noticing
several Projects declaring a Milestone API driver as a Release Candidate
in the checklists.  A Milestone driver is not sufficient for this
requirement.  We need a Release Candidate driver.  We discussed
this at last week's Platform Call (Jan 15), but I was negligent on sending
out a note.  My apologies.

This first came
up with theWeb Socket effort.
 You'll notice that at first I was okay with accepting Milestone builds
as Release Candidates.  But, on the call, I was educated on the difference
expectations between the two types of builds.  With a Milestone build,
it's a step towards a Release.  Each Project could define their own
Milestones and associated builds and content.  Nobody knows if these
are complete enough for public consumption -- unless you are intimate with
the Project.  With a Release Candidate build, the Project has publicly
declared that they are complete enough for public consumption, and that
sufficient progress is being made towards the final Release.

https://github.com/orgs/eclipse-ee4j/projects/17#column-7346435

It's great that
we're getting several Projects with Milestone builds of their APIs -- especially
all of the "web container" APIs.  But, we really need to
push towards Release Candidate builds so that everyone can start using
them -- not only within Jakarta EE, but also tools that are being developed
for Jakarta EE.  Thanks for your cooperation!

---------------------------------------------------
Kevin Sutter 
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter