...
- A design pattern or methodology which must be followed for any new code associated with a new container(s).
- To establish something as a TSC Best Practice the team requesting it are required to:
- open a REQ Jira describing the request.
- present their proposed best practice to the PTLs
- incorporate any feedback and/or clarifications
- into the proposal
- request the TSC to review and approve it as a best practice.
- A Best Practice can be approved by the TSC at any time, but must be approved at or before the M1 milestone for it to be applicable to that release cycle.
- Once approved as a TSC Best Practice it is carried forward for every subsequent release. , unless other action is taken by the TSC.
TSC Global Requirement
- Prior to the Honolulu release, these were commonly referred to as "TSC Must-Haves" and usually specific to that release.
- From Honolulu onwards, a TSC Global Requirement is a was formalized to be any previously approved TSC Best Practice that must be applied to whole code base beginning with a particular release .
- To establish a TSC Global Requirement the team requesting it must must:
- present their previously approved best practice to the PTLs in the context of promoting it to a a Global Requirement beginning with the appropriate release.
- incorporate any feedback and/or clarifications into the proposal
- Any feedback or clarifications need to be incorporated and then a request is made of the TSC to review and approve it.
- A TSC Global Requirement Global Requirement can be approved by the TSC at any time, but must be approved at or before the M1 milestone for milestone for it to be included in applicable to that release cycle.
- Once approved as a TSC Global Requirement it is carried forward for every subsequent release.
...