Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-pmc] Release process

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

I missed this when I updated the handbook after our last update to the process. I'll fix it now.

Wayne



On Sun, Jan 12, 2020 at 6:30 AM Christian Kaltepoth <christian@xxxxxxxxxxxx> wrote:
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.28 but 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
_______________________________________________
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


--
The Eclipse Management Organization
Eclipse Foundation

Back to the top