Each PM was asked to add a code signing item to their checklist/backlog - - it's in your plan for your next release, and you are tracking it according to the process in word doc in item #70 above.
When complete & mandatory, add links to the UFO (Upcoming Feature Overview) document, FTS (Feature Test Summary), blogs post issues(s), and Aha (externally raised RFEs):
UFO:
FTS:
Beta Blog Post (if applicable):
Blog Post:
Aha:
Also, add a comment into the Aha idea linking to this issue.
List of Steps to complete or get approvals / sign-offs for Onboarding to the Liberty release (GM date)
Instructions:
Do the actions below and mark them complete in the checklist when they are done.
Make sure all feature readiness approvers put the appropriate tag on the epic to indicate their approval.
Design
Before Development Starts or 8 weeks before Onboarding
[ ] ID Requirements identified (Documenting Open Liberty). (Epic owner / Feature owner with ID focal point)
[ ] Create a child task of this epic entitled "Feature Test Summary" via this template. Add the link in above.
Before proceeding to any items below (active development), this feature MUST be prioritized on the backlog, and have been socialized (e.g., UFO Review). Follow the Feature and UFO Approval Process.
Development
When active development has begun
[ ] Add the "In Progress" label to this issue.
Beta
If your feature, or portions of it, are going to be included in a beta
Before Onboarding the beta
[ ] Beta Fence the functionality (kind=beta, ibm:beta, ProductInfo.getBetaEdition())
[ ] Identify all open source libraries that are changing or are new. Work with Legal Release Services (Cass Tucker or Release PM) to get open source cleared and approved. Or N/A. (Epic Owner). New or changed open source impacts license and Certificate of Originality.
Translation
3 weeks before Onboarding
[ ] All new or changed PII messages are checked into the integration branch, before the last translation shipment out. (Epic Owner)
[ ] All function tests complete. Ready for FAT Approval. (Epic owner / Feature owner)
[ ] Review all known issues for Stop Ship. (Epic owner / Feature owner / PM)
Focal Point Approvals
2 to 1 week before Onboarding
You MUST have the Design Approved or No Design Approved label before requesting focal point approvals.
All features (both "Design Approved" and "No Design Approved")
[ ] FAT - (OpenLiberty/fat-approvers). SOE FATS are running successfully or N/A . Approver adds label focalApproved:fat to the Epic in Github.
[ ] Demo - (Tom Evans or Chuck Bridgham). Demo is scheduled for an upcoming EOI. Approver adds label focalApproved:demo to the Epic in Github.
[ ] Globalization (Sam Wong - Liberty / Simy Cheeran - tWAS). Translation is complete or N/A. TVT - complete or N/A. Approver adds label focalApproved:globalization to the Epic in Github.
"Design Approved" features
[ ] Accessibility - (Steven Zvonek). Accessibility testing is complete or N/A. Approver adds label focalApproved:accessibility to the Epic in Github.
[ ] ID - (Karen Deen). Documentation work is complete or N/A . Approver adds label focalApproved:id to the Epic in Github.
[ ] Performance - (Jared Anderson). Performance testing is complete with no high severity defects or N/A . Approver adds label focalApproved:performance to the Epic in Github.
[ ] Serviceability - (Don Bourne). Serviceability has been addressed.
[ ] STE - (Swati Kasundra). STE chart deck is complete or N/A . Approver adds label focalApproved:ste to the Epic in Github.
[ ] SVT - (Brian Hanczaryk - APS). SVT is complete or N/A . Approver adds label focalApproved:svt to the Epic in Github.
Ready for GA
1 week before Onboarding
[ ] No Stop Ship issues for the feature. (Epic owner / Feature owner / Release PM)
[ ] Github Epic and Epic's issues are closed / complete. All PRs are committed to the release branch. (Epic owner / Feature owner / Backlog Subtribe PM)
Description of the high level feature, including any external spec links:
This has been requested by Emily Tuczkowski/Austin/IBM. Code signing must be implemented by each product. See https://github.ibm.com/WAS-CD-Subtribe/WAS-CD-Subtribe/issues/70 for more details.
Each PM was asked to add a code signing item to their checklist/backlog - - it's in your plan for your next release, and you are tracking it according to the process in word doc in item #70 above.
This issue is tracking code signing for Liberty (currently marked as not done): https://github.ibm.com/SPbD-at-IBM/Issues/issues/306 We need to work a plan to complete.
Box note for list of products and info on Code signing: https://ibm.ent.box.com/notes/824704551383
When complete & mandatory, add links to the UFO (Upcoming Feature Overview) document, FTS (Feature Test Summary), blogs post issues(s), and Aha (externally raised RFEs):
UFO:
FTS:
Beta Blog Post (if applicable):
Blog Post:
Aha:
List of Steps to complete or get approvals / sign-offs for Onboarding to the Liberty release (GM date)
Instructions:
Design
Before Development Starts or 8 weeks before Onboarding
Before proceeding to any items below (active development), this feature MUST be prioritized on the backlog, and have been socialized (e.g., UFO Review). Follow the Feature and UFO Approval Process.
Development
When active development has begun
Beta
If your feature, or portions of it, are going to be included in a beta
Before Onboarding the beta
kind=beta
,ibm:beta
,ProductInfo.getBetaEdition()
)1 week before beta GA
Legal
3 weeks before Onboarding
Translation
3 weeks before Onboarding
Feature Complete
2 weeks before Onboarding
Focal Point Approvals
2 to 1 week before Onboarding
You MUST have the Design Approved or No Design Approved label before requesting focal point approvals.
All features (both "Design Approved" and "No Design Approved")
"Design Approved" features
Ready for GA
1 week before Onboarding
1 week before GA
Other deliverbles