| Re: [jakarta.ee-spec] Separate the post ballot checklist into one for the mentor and one for project team |
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
to separate out the post ballot concerns as we talked about on Wed. There is now a checklist for the mentor and one for the project team that the mentor is to put into a specification project team issue for tracking._______________________________________________ jakarta.ee-spec mailing list jakarta.ee-spec@xxxxxxxxxxx To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec__;!!GqivPVa7Brio!M65SvRCUEdbjRseogWTZXUO9sWpMzjNrtHn4XsMub4xy5pHVilaj2Bfn4UdrFmy4FVk$