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'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?
_______________________________________________
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
