Skip to end of banner
Go to start of banner

DR-000033 - Process for Managing Tools/Dependencies/Frameworks

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Submitted DateTBD
Approved Date
StatusDRAFT
ImpactHIGH

 

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

Radhakrishnan Gopalakrishnan 

Approvers


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

Refer to the Objective 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
    • N/A
  • Cons
    • N/A

Other Related Resources

Component Owners

Managing Tools/Frameworks/Dependencies Version - v0.2 DRAFT

  • No labels