Re: [jakarta.ee-spec] Separate the post ballot checklist into one for th

[Ivar Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx>]

I also submitted a PR which adds a step that we need to notify the EMO with the ballot results on ballot completion.

Ivar

On Thu, Sep 3, 2020 at 6:35 PM Scott Stark <starksm64@xxxxxxxxx> wrote:

Ok, I created the following issue to discuss at the next spec committee call:

https://github.com/jakartaee/specification-committee/issues/39

On Thu, Sep 3, 2020 at 11:26 AM Lukas Jungmann <lukas.jungmann@xxxxxxxxxx> wrote:

On 9/3/20 6:03 PM, Scott Stark wrote:
> I have update the spec finalization checklist doc:
> https://github.com/jakartaee/specification-committee/blob/master/spec_finalization_checklist.md
> <https://urldefense.com/v3/__https://github.com/jakartaee/specification-committee/blob/master/spec_finalization_checklist.md__;!!GqivPVa7Brio!M65SvRCUEdbjRseogWTZXUO9sWpMzjNrtHn4XsMub4xy5pHVilaj2Bfn4Udru7LhWMI$>

the checklist says:
"A Release Review is not required if the current release is a Service
Release based on a previously successful Major or Minor release"

the handbook[1] says:
"Specification project teams must engage in a release review prior to
every release (including service releases);"

Would it be possible to align this somehow?

thanks,
--lukas

[1]:
https://www.eclipse.org/projects/handbook/#specification-project-reviews

_______________________________________________
jakarta.ee-spec mailing list
jakarta.ee-spec@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec

--

Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation, Inc.

Community. Code. Collaboration. 

Join us at our virtual event: EclipseCon 2020 - October 20-22