-
Notifications
You must be signed in to change notification settings - Fork 591
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support gRPC / gRPC-java #8637
Comments
Documentation work that we'll require: OpenLiberty/docs#2698 |
WAD review actions / comments from 11/4/2019 come-back review:
Note that the consensus on the call was to focus on using a Servlet for the inbound path. This is easier for us to code, although it may make sharing code with Quarkus more difficult. We can cross that bridge when we get there. |
@pnicolucci Why would this be documented in WebSphere traditional documentation when it is for Open Liberty? |
@NottyCode I closed the twas doc issue, at one point in time I believe that is where ID wanted us to open the issues for docs, we can work with ID and get an issue opened in the open liberty repo instead. |
Per discussion with @steven1046, from the accessibility point of view |
L2 has requested STE slides for this feature. The STE template can be found at the links below. You can use either one to create the education. Slide Template: https://ibm.box.com/s/1an42g7zdgmaj84w7dft0indqfgi8ffm Github Template: https://pages.github.ibm.com/WASL3/site/STE/about Please upload the completed slides to the same STE Archive BOX folder or provide me the Github link. Thanks! |
Serviceability Approval Comment - Please answer the following questions for serviceability approval:
b) Who did you demo to?
c) Do the people you demo'd to agree that the serviceability of the demonstrated problem scenarios is sufficient to avoid PMRs for any problems customers are likely to encounter, or that L2 should be able to quickly address those problems without need to engage L3?
b) Do they agree that the serviceability of the problems they encountered is sufficient to avoid PMRs, or that L2 should be able to quickly address those problems without need to engage L3?
|
List of Steps to complete or get approvals / sign-offs for Onboarding to the Liberty release (GM date)
Instructions:
TARGET COMPLETION DATE Before Development Starts or 8 weeks before Onboarding
TARGET COMPLETION DATE 3 weeks before Onboarding
TARGET COMPLETION DATE ** 3 weeks before Onboarding**
TARGET COMPLETION DATE 2 weeks before Onboarding
APPROVALS with TARGET COMPLETION DATE 2 to 1 week before Onboarding
Prereq: You must have the Design Approved or No Design Approved label on the GitHub Epic.
TARGET COMPLETION DATE 1 week before Onboarding
NOT REQUIRED FOR A FEATURE
Related Deliverables TARGET COMPLETION DATE General Availability
Design document: https://ibm.box.com/shared/static/x6vy73iadmip6ix00mzhwuz2vqgqr4x2.pptx
The text was updated successfully, but these errors were encountered: