Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-pmc] Jakarta EE releases in Maven Central
It’s even worse. Today 3 artifacts hit the Maven Central:

jakarta.persistence   jakarta.persistence-api     2.2.1 | (1)     02-Nov-2018     
jakarta.ejb           jakarta.ejb-api           3.2.3 | (1)     01-Nov-2018     
jakarta.annotation    jakarta.annotation-api    1.3.3 | (1)     29-Oct-2018

It was done by mistake. We understand the process and know that public releases cannot be done without passing the release review. Wayne, how shall we deal with this situation?

Thanks,
Dmitry

On 2 Nov 2018, at 14:15, Ivar Grimstad <ivar.grimstad@xxxxxxxxx> wrote:

I have added this item to the PMC meeting on Tuesday.

Ivar

On Fri, Nov 2, 2018 at 2:12 PM Kevin Sutter <sutter@xxxxxxxxxx> wrote:
You are correct, Christian.  The Eclipse Release Review should be successful before the artifacts are published to Maven Central.

I'm going to chalk this up to a new process.  Everybody has been pushing to complete this Glassfish release and the process may not be well understood by everybody.  (Although the EclipseLink team should know the process...)

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



From:        Christian Kaltepoth <christian@xxxxxxxxxxxx>
To:        EE4J PMC Discussions <ee4j-pmc@xxxxxxxxxxx>
Date:        11/02/2018 07:55 AM
Subject:        [ee4j-pmc] Jakarta EE releases in Maven Central
Sent by:        ee4j-pmc-bounces@xxxxxxxxxxx



Dear PMC,

I'm a bit confused. It looks like more and more Jakarta EE releases are available in Maven Central:

EJB: https://search.maven.org/search?q=g:jakarta.ejb
JPA: https://search.maven.org/search?q=g:jakarta.persistence

But AFAIK there were no Release Reviews for these releases. My impression was that releases are first pushed to the staging repository and then a corresponding Release Review is created. And only if the Release Review is successful, the artifacts a pushed to Maven Central. 

Is that correct? Or am I missing some part of the process here?

Best regards

Christian


--
Christian Kaltepoth
Blog: http://blog.kaltepoth.de/
Twitter: http://twitter.com/chkal
GitHub: https://github.com/chkal
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc



_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc
--

Java Champion, JCP EC/EG Member, EE4J PMC, Jakarta EE WG Member, JUG Leader

_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc

Back to the top