Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-pmc] [jakarta.ee-community] Release process
And note that specification releases still require a review for every release.  The CI might not require a review but the specification will.  (I don't think the below is talking about specification releases, but I just wanted to include this so no one is confused.)

Kevin Sutter wrote on 1/13/20 7:13 AM:
Looks like the wrong "community" mailing list was being used in this string, so I'll correct that to the Jakarta EE Community to give a wider distribution.  I will also copy in the Jersey Dev mailing list to let them know that they are part of this discussion...  :-)

---------------------------------------------------
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



From:        "Kevin Sutter" <sutter@xxxxxxxxxx>
To:        EE4J PMC Discussions <ee4j-pmc@xxxxxxxxxxx>
Cc:        EE4J community discussions <ee4j-community@xxxxxxxxxxx>
Date:        01/13/2020 08:57
Subject:        [EXTERNAL] Re: [ee4j-pmc] Release process
Sent by:        ee4j-pmc-bounces@xxxxxxxxxxx



Hi Christian,
The Project Handbookindicates that a successful release review allows a project to distribute new major or minor releases for up to one year:

"A project team may declare official major or minor releases and distribute associated products for up to one year following a successful release or progress review. Reviews are not required for bug-fix/service releases."

So, based on that, the Jersey project was okay with their 2.29 and 2.29.1 releases, but the 2.30 release needs to have a successful release review.  The project seems to be in a state of flux since the 2.30 release is not officially marked as a public release yet in github...  https://github.com/eclipse-ee4j/jersey/releases.  There is a tag for it, but not a release...

Bottom line, Christian, I think your understanding is correct and Jersey needs to tidy things up a bit.  We do have to remember that the Eclispe processes are new to most of us, so there will be some hiccups along the way while we all get our feet wet.  Thanks!

---------------------------------------------------
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



From:        "Steve Millidge (Payara)" <steve.millidge@xxxxxxxxxxx>
To:        EE4J PMC Discussions <ee4j-pmc@xxxxxxxxxxx>
Cc:        EE4J community discussions <ee4j-community@xxxxxxxxxxx>
Date:        01/13/2020 06:19
Subject:        [EXTERNAL] Re: [ee4j-pmc] Release process
Sent by:        ee4j-pmc-bounces@xxxxxxxxxxx

I am not an expert on the process so I could be wrong but my understanding is that once a project has a successful release review it can make further releases for a year without a formal review. I assume a release record is still required though but Wayne or Ivar can correct me.

 

I just googled and this blog seems to also say the same https://blogs.eclipse.org/post/wayne-beaton/progress-and-release-reviews

 

Steve

 

From:ee4j-pmc-bounces@xxxxxxxxxxx <ee4j-pmc-bounces@xxxxxxxxxxx> On Behalf Of Christian Kaltepoth
Sent: 12 January 2020 11:30
To: EE4J community discussions <ee4j-community@xxxxxxxxxxx>; EE4J PMC Discussions <ee4j-pmc@xxxxxxxxxxx>
Subject: [ee4j-pmc] Release process

 

Hi all,

 

I'm currently working on the first Eclipse Krazo release. As this is our first release under the umbrella of the EE4J project, I would like to ask a few questions about the process, especially regarding release reviews.

 

I just checked the project site of Eclipse Jersey, because I was interested to see how other projects are doing it. Eclipse Jersey published versions like 2.28, 2.29 or 2.29.1. So it looks like they are following the "major.minor" and "major.minor.patch" versioning scheme. The Eclipse Project Handbook states:

 

All major and minor releases require a review. Service releases [...] do not require a review.

 

There was a release review for the 2.28 release. That's fine. But there wasn't one for the 2.29 release. But isn't this required for a non-service release? There is also only an IP Log for 2.28but not for 2.29.

 

Also, Eclipse Jersey released 2.30 a few days ago and the release is already available in Maven Central. However, there isn't any entry for 2.30 in the "Latest Releases" table on the Jersey project site. So it looks like there isn't any release plan and also no release review for 2.30.

 

Am I missing something here?

 

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




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

Back to the top