Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Table of Contents

Planned deadlines

MilestonePlanned deadlineActual deadlineDescription of the MilestoneComments
M0date as initially planneddate as really committed
  • Declaration of participation in the simultaneous release
    • Blueprint proposal represented as a Jira EPIC ticket
    • Feature lead assigned to Jira Epic ticket - declaration of participation in the simultaneous release
    • The initial version of Increment Blueprint stored on github/tf-spec/Release folder,
    • The blueprint presented, discussed and approved by related
    , agreed, approved by TSC
    • The initial version of the Release Plan for the project presented
    • Dependencies between projects/components/areas identified
    Participating projects and initial Release scope approved by TSC 
    problems, decisions, reasons for the delay, etc

    • All dependencies between existing functionality and requested change/feature discussed and agreed by PTL and related approvers (based on Modules/Commiters)
    • Jira Epic ticket broken down into stories in related Jira project (backlog, plan) - presented and discussed on TWS meeting
    • The final version of Blueprints, Release Scope and Release Plans for participating projects discussed and approved by approvers


    • Technical design fully provided, agreed (documentation on the Confluence/github/tf-spec available)
    • Jira Epic ticket updated with link to technical design
    • Documentation started
    • Feature tests started
    • Feature/Functionality Freeze - Technical Design approved by relevant approvers (Modules/Commiters)


    • External API available for beta-tests
    • Jira Epic ticket updated with information about API availability (documentation link - tf repo)
    • Documentation in progress
    • Tests in progress
    • API Freeze confirmed by Feature Lead (comment on Jira Epic ticket with repo/commit ID link)


    • all functionality and APIs available for testing
    • Jira Epic ticket updated with information about final API documentation, executed UI tests documentation
    • Documentation provided - confirmed by Documentation project PTL
    • Code freeze confirmed by Feature Lead (comment on Jira Epic ticket) - only bug fixing allowed


    • Release candidates agreed, approved, tested
    • System tests conducted, quality confirmed by CI/CD PTL (should we have some QA? Security?)
    • Final documentation provided, reviewed, approved by Documentation PTL
    • Marketing information provided to Marketing Advisory Council - confirmed by Brandon Wick?
    • release branch cut off - branch stabilization from now on
    • Release Candidates freeze, confirmed by PTL and TSC(?)


    official deployment executed

    Planned scope

    Project Name (link)Overall description of the project's increment in the particular release
    • Dependent on: projects, on which this increment relay on
    • Affect: projects which depend on this increment