I can share individual files, but not folders.
Can someone on the Eclipse side add Kevin to the top level "Jakarta EE Specification Committee" team drive? Or at least to the TCK Process folder I created? Tom Snyder <tom.t.snyder@xxxxxxxxx> also needs access.
I also cannot delete files, so if someone can delete this one that'd be appreciated. I didn't end up needing it:
- https://docs.google.com/document/d/1I1-8f6pQUyIpnA6TpNH0bK69Gp-Qb_i7PeCZipfrOJY/edit
-- David Blevins 310-633-3852
David,I need access to the doc link you provided
(kwsutter@xxxxxxxxx). Thanks!I appreciate the "homework"
and prep work for next week's call. But, there are several other
participants on the Spec call familiar with the TCK processes. IBM
is well versed on this topic and I, personally, have been directly involved
in the CTS testing since J2EE 1.4. Red Hat is also very much involved
with the CTS process, as well as Fujitsu. So, I think we have several
"parents" to choose from... :-)Just wanted to clarify that I think
we have plenty of varied experience on the Spec Committee to produce the
right solution without having to "choose sides".
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Java EE architect
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutterFrom:
David Blevins <dblevins@xxxxxxxxxxxxx>To:
Jakarta specification
committee <jakarta.ee-spec.committee@xxxxxxxxxxx>Date:
12/05/2018 05:35 PMSubject:
[jakarta.ee-spec.committee]
Understanding the Current Specification ProcessSent by:
jakarta.ee-spec.committee-bounces@xxxxxxxxxxx
The current status of basically only Bill and I being
deeply familiar with the TCK process I think is a major hinderance. I
think if we were to venture forward in the current state, it would result
in a conversation primarily between Bill and I and you all feeling like
you had to pick between your favorite parent. I like Bill far too
much for that. You all need your own experience or as close to it
as you can get.
In that vein I've attempted to put together a crash course of actual TCK
challenges, exclude lists, and file names from Apache's and my own experience
with the certification process.
- https://docs.google.com/document/d/1CAnAYCtafDuf_s4DQhUZEIPO0GBOaT48X74N8LUQh-w/edit#
I ask you all to spend time reviewing the material in advance of next week's
call. We can spend some time discussing it in more detail when we're
together.
Once we all have at least some virtual experience with real details and
real challenges, we can begin to form our own opinions and make true progress.
I think if we start defining a process now, we'd be starting "in
the middle" and would not be able to resolve with confidence or in
any reasonable time.
This is still just a portion of the story. CDI and Bean Validation
have the same concepts but implemented entirely differently. They
also have their own document on how they prefer their process to work.
MicroProfile also has it's own process, less defined than CDI, but
still third generation in many ways.
So our and your homework will be:
1. Understand the Sun/Oracle TCK process and materials
2. Understand the CDI/Bean Validation TCK process and materials
3. Understand the MicroProfile TCK process and materials
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
310-633-3852
_______________________________________________
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
_______________________________________________ jakarta.ee-spec.committee mailing list jakarta.ee-spec.committee@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
|
