Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec.committee] meeting Friday 9:00am PDT
Yes.


---------------------------------------------------
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:        Ed Bratt <ed.bratt@xxxxxxxxxx>
To:        Kevin Sutter <sutter@xxxxxxxxxx>
Cc:        Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Date:        09/06/2019 10:56 AM
Subject:        [EXTERNAL] Re: [jakarta.ee-spec.committee] meeting Friday 9:00am PDT



Does Liberty team intend to remove the DI issue from the certification request (and presumably in the certification summary page that is yet to be published)? Seems like that ought to be within their permissions.
- Ed
On 9/6/2019 8:39 AM, Kevin Sutter wrote:
Hi Ed,
We are working on the publishing of the TCK Results.  Should be there before EOD today.  Sorry for the delay, but with the updated TCK, it's taking a bit to run the full bucket again and verify the results.

It doesn't look like we can close the DI Challenge issue.  Not enough permissions.  I posted the following description to the issue and asked for the Challenge to be closed.
https://github.com/javax-inject/javax-inject/issues/39#issuecomment-528903591

I fully agree that the Platform should not approve the CR until we get the results posted.

---------------------------------------------------
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:        Ed Bratt <ed.bratt@xxxxxxxxxx>
To:        Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>, Kevin Sutter <sutter@xxxxxxxxxx>
Date:        09/06/2019 10:25 AM
Subject:        [EXTERNAL] Re: [jakarta.ee-spec.committee] meeting Friday 9:00am PDT



The certification request is still incomplete.
  • The TCK summary report for Liberty is not yet included in the issue
  • I was agreed we would provide an updated exclude list for the issues reported against JSONB.
    • This is in the works. A proposed update to the CTS was staged yesterday. We are still completing analysis of the staged TCK and expect to propose adoption once that's complete.
  • Liberty team was going to remove the exception request for Jakarta Dependency Injection.
  • The resolution taken by Steering Committee hasn't really been publicized and/or that data about the signatures is not available for the Liberty certification.
The Platform team can decide what it wants to do, but I would note that the data are not yet complete to approve the request. Are the actions listed above correct and complete? Does the requester know when these issues will be resolved? I would recommend these details be provided in the certification data and/or the request issue.
-- Ed
On 9/6/2019 7:43 AM, Kevin Sutter wrote:
FYI, Here is the update to the JSF Signature challenge that we discussed yesterday...
https://github.com/eclipse-ee4j/faces-api/issues/1474#issuecomment-528880074

We will update our TCK Results for Open Liberty to include these failures and provide a reference to the Challenge.

---------------------------------------------------
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:        Paul Buck <paul.buck@xxxxxxxxxxxxxxxxxxxxxx>
To:        Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Date:        09/06/2019 08:22 AM
Subject:        [EXTERNAL] Re: [jakarta.ee-spec.committee] meeting Friday 9:00am PDT
Sent by:        jakarta.ee-spec.committee-bounces@xxxxxxxxxxx




Thanks for the update. 

Amazing teamwork here to resolve the situation. A big thanks to Team Oracle!

I will delete the call today at 900AM pacific time.

... P


On Fri, Sep 6, 2019 at 8:44 AM Kevin Sutter <sutter@xxxxxxxxxx> wrote:
The Plan A for JSON-B seems to be working.  The updated TCKs were communicated to all of us yesterday and we've (Open LIberty) been running with the updated TCK.  So, this is all looking good.  Thanks to the Oracle test teams for doing this on such short order!

We have also been able to run the DI TCK against the Weld binaries, so we have results for that as well.

And, we should have the failing JSF signature tests to post once our run is complete.  

So, unless someone has other issues to discuss, I think we're good from an Open Liberty perspective.

---------------------------------------------------
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:        Paul Buck <paul.buck@xxxxxxxxxxxxxxxxxxxxxx>
To:        Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Date:        09/06/2019 06:21 AM
Subject:        [EXTERNAL] Re: [jakarta.ee-spec.committee] meeting Friday 9:00am PDT
Sent by:        jakarta.ee-spec.committee-bounces@xxxxxxxxxxx




Have we resolved the certification situation with Open Liberty? The call was put on our calendars to work on Plan B. If required.

See Proposal in the minutesfrom the Spec Committee call on Wednesday.


On Fri, Sep 6, 2019 at 2:19 AM Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:

I haven't seen a cancellation so I'm assuming we're meeting tomorrow.
It would be nice to have an agenda, however...
_______________________________________________
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@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@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@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@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





Back to the top