Page tree
Skip to end of metadata
Go to start of metadata

Introduction

  1. A blueprint is an initial version of a proposal for the new feature, problem solution which is intended to be covered in the particular release. 
  2. It needs to be well described to allow approvers and all the TF Community members to understand the intention of requesters. Ideally, the request should be based on the Blueprint template.
  3. The requested blueprint must have the Blueprint/Feature Lead - a one person responsible for delivering all needed documentation, explanations, and also responsible for proper reflecting of achieved milestones of requested change in the TF Jira Feature project.

Process

  1. Feature Lead registers an JIRA EPIC ticket reflecting requested blueprint/feature in the backlog of the TF Jira Feature project.
    • meaningful name of the epic
    • meaningful description + link to confluence blueprint page or Markdown (.md) file in https://github.com/tungstenfabric/tf-specs repo in R2011/TFF-XX subfolder
    • Feature lead as assignee.
  2. Feature Lead provides properly filled Blueprint template stored as a sub-page for the particular Release Overview page (e.g. 2011 Release Overview) or Markdown (.md) file in https://github.com/tungstenfabric/tf-specs repo in R2011/TFF-XX subfolder - link provided in Jira Epic ticket
  3. When Blueprint is ready to be assessed, the Feature Lead moves reflecting Jira ticket to Selected for TSC discussion column in the Kanban board of the TF Jira Feature project.
  4. The release Manager formally reviews the requested blueprint (template properly filled, all needed information provided) and assigns Approvers/Committers based on a list of affected Modules. Committers to approve the requested Blueprint are directly derived from the affected Modules. Nominated Committers are informed via email 
  5. Committers review the blueprint, assumptions, intended solution, dependencies, and alignment with the current TF architecture. 
    1. in case of doubts, discovered gaps Committer contacts directly with the Blueprint/Feature Lead to clarify, update, improve the blueprint
    2. Committers should provide their feedback or approval within two weeks from the notification
  6. If there are no negative feedback or pending explanations the Release Manager moves Jira Epic ticket representing the blueprint to the M0 achieved column and adds the Release name to the fix version field 
  • No labels