Re: [jakartaee-spec-project-leads] Staging repo advice required

[David Blevins <david.blevins@xxxxxxxxx>]

> On Dec 21, 2019, at 11:32 AM, Mark Thomas <markt@xxxxxxxxxx> wrote:
> 
> Hi,
> 
> To make progress converting the JSP API, I need jakarta.* versions of
> the dependencies: EL and Servlet. While EL might not be quite ready for
> release (I haven't done a careful check that i's are dotted and t's are
> crossed) I do believe it is ready enough for JSP to build against.
> 
> Should I deploy EL 4.0.0 to the staging repo as if it were a release
> candidate but with the expectation I'll drop the staging repo and
> redploy at least once before the actual release (commenting out the part
> of the CI script that commits the updated pom.xml)? Or should I do
> something else? If so, what?

I don't know if the specifics of what extension should be used, but the approved Jakarta EE 9 release plan does allow you to put release candidates or some form of non final builds out to Maven Central.  Something like "4.0.0-rc1", "4.0.0-m1" or some clearly non-final designation.

The motivation being basically what you state: good enough to allow us to take more steps and unblock other dependent specs and implementations, but perhaps not perfect enough for a final (which also requires all the spec, TCK and one implementation to be ready for final).

Theoretically at some point in the future when we're following our EFSP a little more strictly, Milestone Builds would actually be a requirement leading up to a final:

 - https://www.eclipse.org/projects/efsp/#efsp-reviews-progress

I think where that puts you is as long as it's clearly not a final release, you have enough flexibility to ask for forgiveness vs permission.  Regular project vote on proposed rc or milestone binaries is fine.  If someone doesn't like the exact extension you choose, we'll iterate and get better.

My $0.02 at least :)


-David