...
| Page Properties | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Overrides/Supersedes
N/A
RFC
N/A
Stakeholders
@mention individual(s) who has vested interest in the DR. This helps us to identify who needs to be aware of the decision
Contributors
Approvers
List TC members voted to approve the change
Background/Context
Explain the need that triggered the need for making a decision
Assumptions
List all assumptions that were made when making the decision
Constraints
List any constraints that lead us to make a certain decision
Rationale
Document the thought process, list reasons that lead to the final decisionRefer to the Assumptions section of the process document
Constraints
N/A
Rationale
Refer to the Objectives section of the process document
Decision
Following are the key decision points related to the process
- Tools/Technologies/Frameworks WILL be assigned an owner
- Component owner works with release coordinator to create tickets within the scope of the release and the teams will come with execution plan and decide on committing to the work
- TC will review/weigh in/approve plans for major infrastructure components and shared tooling
Implications
- Pros
- Provide a link to RFC when applicableN/A
- Cons
- Provide a link to RFC when applicableN/A