Hi Santiago,
I agree that is complex for specification projects. A lot of this is down to the fact that a specification project is special. The specification process release review is defined here
https://www.eclipse.org/projects/efsp/?version=1.2#efsp-reviews-release and the various checklists are maintained by the specification committee here
https://github.com/jakartaee/specification-committee
The specification process defines that the EMO, PMC and a ballot of the specification committee all have to be successful for a spec to be released. I assume the PMC and EMO approvals are inherited
from the standard Eclipse release reviews that all projects have to undergo.
What the spec committee need to do (if they haven’t already) is a set of simple steps which detail what is needed to meet the needs of the EFSP release review and in what order so it doesn’t feel
like a black art.
Steve
From: ee4j-pmc-bounces@xxxxxxxxxxx <ee4j-pmc-bounces@xxxxxxxxxxx>
On Behalf Of Santiago Pericas-Geertsen
Sent: 26 October 2020 14:12
To: EE4J PMC Discussions <ee4j-pmc@xxxxxxxxxxx>
Subject: Re: [ee4j-pmc] Jakarta REST 3.0 Review
Hi Ivar,
The whole release process seems very convoluted, especially for those that aren’t in the day-to-day discussions related to it. There’s multiple PR’s with long checklists, multiple e-mails, reviews, etc. By contrasts, a release in the JCP
days was a lot simpler.
I fear this process will discourage projects from releasing often (I certainly feel that way), and just prevent Jakarta EE to evolve at the “desired” pace. I hope we can figure out a simpler process going forward. I don’t pretend to have
a holistic view of the process to provide any actual recommendation, but my point of view, it looks unnecessary complicated.
No questions are dumb! ;)
I must say that I am a little unsure which review period you are referring to that has ended...
The Ballot will conclude on November 3rd.
The proposed release date is set by the project team to October 30 in the release record. This is the date that probably should be adjusted by the project team. If it feels better,
go ahead and do so.
This is the date the EMO will conclude its release review, but since it depends on the ballot, that won't happen until November 3rd.
There are so many moving parts here that I am sure there are some small inconsistencies and chicken-and-egg situations here and there. We just need to be a little pragmatic when it
comes to some of the less important details.
Thank you for this information, Ivar.
Maybe this is a dumb question, but what sense does it make to end the review period earlier than the ballot period…?
-Markus
As you can see from the release record by the EMO, the status is pending, since it depends on the review mentioned
above.
--
Jakarta EE Developer Advocate | Eclipse
Foundation, Inc.
Community. Code. Collaboration.
Join us at our virtual event: EclipseCon
2020 -
October 20-22
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/ee4j-pmc
--
Jakarta EE Developer Advocate |
Eclipse Foundation, Inc.
Community. Code. Collaboration.
Join us at our virtual event:
EclipseCon
2020 - October 20-22
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/ee4j-pmc__;!!GqivPVa7Brio!OV5ttdADT4Ds6F9FCeFxR-L_Ra_RlQ0u6GnHXNI5tANGvKpWGTxuutzGIiVv944zYA12cmN84A$
|
