Re: [jakarta.ee-spec.committee] Jakarta-ized Specs a requirement for Jak

["Kevin Sutter" <sutter@xxxxxxxxxx>]

Bill,
The Update Calls
are recorded:
https://www.youtube.com/playlist?list=PLy7t4z5SYNaSY0Um6Vbez3G5Lc2AMaMw7

The concern with
the Jakarta-izing the specs was just the amount of work.  Not that
it was difficult, just time consuming to get it right.

I agree with the
"strongly encourage" statement.


---------------------------------------------------
Kevin Sutter 
STSM, MicroProfile and Jakarta EE architect
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter



From:
       Bill
Shannon <bill.shannon@xxxxxxxxxx>
To:
       Jakarta
specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>,
Kevin Sutter <sutter@xxxxxxxxxx>
Date:
       11/16/2019
17:53
Subject:
       [EXTERNAL]
Re: [jakarta.ee-spec.committee] Jakarta-ized Specs a requirement for Jakarta
EE 9?

---

I agree that we shouldn't require it,
although it should be strongly encouraged.

If any changes are made other than just the package name change, it should
very very strongly be encouraged.  And the spec committee is always
free to review the changes to a particular API and say "I don't understand
how the updated API works, you need more documentation than just the javadocs".

(Is there a recording of the Update call?  I was confused about the
time of the meeting and missed it.  I'd like to understand why updating
the docs to Jakarta-ize them is difficult.  Ya, I'm sure the quantityof work required is quite large in some cases, but I didn't expect it to
be complicated to figure out how to do the updates.  Kevin, did you
consider the updates to the platform spec to be difficult?)


Kevin Sutter wrote on 11/13/19 2:14 PM:
Hi,
For the components that have received and are in the process of jakarta-izing
their specifications from Oracle, are we going to require that this exercise
be completed as part of Jakarta EE 9?  This question indirectly came
to light during out Jakarta EE Update call this morning.  The JAX-RS
team was explaining how much work this was to Jakarta-ize their Spec --
more work than they expected.

Since we didn't require the Spec docs for Jakarta EE 8, I think it would
be a tough sell to require these docs for Jakarta EE 9.  Especially
since we don't know exactly when the rest of the components will be receiving
their document source.  And, if we really want Jakarta EE 9 to be
an early 2020 deliverable, then adding this additional Spec overhead may
be too much.

I wanted to get a reading from this team so that we have a response if
and when this question becomes real.

---------------------------------------------------
Kevin Sutter 
STSM, MicroProfile and Jakarta EE architect
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 change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee