Versions Compared

Key

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

...

  • With each alpha or release-candidate API version, the API version and release tag shall be updated.
  • The actual milestone dates shall be put in the release tracker when the milestone is passed.
  • When M4 is sucessfully successfully passed, the link to the public-release API package shall be added.

...

  • If an API release is not visible, please check that the correct meta-release label is added to the API release tracker page. 

The following are the actions for milestones:

  • M0
    • follows scope definitions of Commonalities and ICM and assess impact
  • M1
    • Create API release tracking page for the API if it does not yet exist
    • Create API release tracker for the API version to be released
    • Define scope of API release:
      • Record scope in dedicated GitHub issue.
      • Update the release tracker with the scope issue link
    • Develop API scope through one or more alpha release(s)
    • Update the API release tracker with each alpha release
    • Create first release-candidate PR and submit to Release Management
    • After Release Management approval:
      • Create first release-candidate for the API
      • Update the API release tracker with the release-candidate tag
  • M2
    • Assess final impact of Commonalities and ICM scope on API(s)
  • M3
    • Fix bugs raised by API testers through one or more release-candidates
    • Update API release tracker with each release-candidate
    • Submit final release-candidate PR to Release Management for checking
    • After final release-candidate PR approval by Release Management:
      • Create final release-candidate and update API release tracker
      • Create API public-release PR
    • After TSC approval of the PR
      • Create public-release
      • Update the API release tracker with public-release tag
  • M4
    • N/A
  • M5
    • Provide feedback on meta-release
  • M6

TSC

  • M0: Declare meta-release kickoff
    • Approve Commonalities and ICM scope
    • Approve final alpha release PRs of Commonalities & ICM
  • M1
    • Approve final release-candidate PRs of Commonalities & ICM
  • M2
    • Reviewing scope of selected APIs (case by case selection)
  • M3
    • Formal approval of the Commonalities & ICM public-release PRs
    • Formal approval API public-release PRs
  • M4
    • Meta-release approval
  • M5
    • Provide feedback on meta-release
    • Meta-release improvements approval
  • M6


Release milestone status

The milestone status values on the meta-release pages are managed by the Release Management team and shall have values defined as follows:

...