[jakarta.ee-spec.committee] Restart Annotations ballot???

["Kevin Sutter" <sutter@xxxxxxxxxx>]

Hi,
The ballot for
Annotations closed today (9 '+1' votes, 1 '-1' vote).  But, when I
was reviewing the PR for the final checklist activities, I noticed that
the javadoc and the staged APIs were updated in the middle of the vote.
 These updates were in response to comments provided with Tomitribe's
'-1' vote.  So, the updates are all good, but they were deemed "nits"
and should have been put on the back burner for the next release of Annotations.

https://github.com/jakartaee/specifications/pull/224

Although the restarting
of the ballot sounds like the logical next step, we don't have this scenario
documented in our ops guide (https://jakarta.ee/committees/specification/operations/).
 So, I wanted to run it by the Spec Committee first before initiating
the restart of the ballot.  While getting this discussed with the
Committee, I'm working with Dmitry to ensure that all of the Tomitribe's
'-1' comments are covered by these updates so that the vote will pass this
next time.

BTW, I want to
highlight that we are *not* treating this '-1' vote as veto and forcing
the restart of the vote.  The plan was to log the -1 vote, log the
comments in the Annotations component, and move on.  Unfortunately,
the comments were accidentally incorporated into the Spec PR and, thus,
is causing this restart.  

If anybody on
the Spec Committee has an issue with this approach, speak up now.  I
want to restart this vote asap.  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