Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec.committee] Losing track of uncompleted checklist items..
I'm leaning towards creating a separate issue against the spec project with the remaining checklist items. Having an uncompleted checklist in a merged PR doesn't seem right to me.

Ivar

On Fri, Aug 28, 2020 at 5:58 PM Kevin Sutter <sutter@xxxxxxxxxx> wrote:
Hi,
Part of our current process is to put a new checklist into the Specification PR as reminder of what needs to be done after a ballot is complete:
https://github.com/jakartaee/specification-committee/blob/master/spec_finalization_checklist.md

This is very helpful.  But, once the Mentor does the third step in the checklist (merging of the PR), the PR is closed and falls off our radar.  Since the mentor is very much aware of the items that still need to be done, I'm not concerned about the mentor completing those tasks.  But, half of the checklist items actually needs the Specification Project team to complete.

Bean Validation is a current example, if you wish to take a look:
https://github.com/jakartaee/specifications/pull/222

A simple way around this is to just move the merging of the PR to the last checklist item and indicate that everything else needs to be completed before the Mentor can merge the PR.  This way we would ensure that everything was completed before closing out the PR.  The con to this approach is that we may be waiting days or weeks before the Spec Project team completes the required tasks. Do we want to hold up the Specification page updates until then?

Another approach would be break up the checklist into two.  One for the Specification PR for the Mentor.  And, create a separate Issue against the Spec Project with the checklist items for the Spec Project (including a link to this new Issue in the Spec PR).  This would allow us to have up-to-date Specification pages in a timely manner, and put the other remaining work items on the shoulders of the Spec Project.

Thoughts or other suggestions?

---------------------------------------------------
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
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee


--

Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation, Inc.

Community. Code. Collaboration. 

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

Back to the top