Versions Compared

Old Version 51

changes.mady.by.user Tanja de Groot

Saved on

compared with

New Version 52

changes.mady.by.user Tanja de Groot

Saved on

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 successfully passed, the link to the public-release API package tag shall be added.

An API version of an API Sub Project should show on the meta-release page as soon as an API release tracker has been created under the API Sub Project's API release tracking page for the API version planned to be released in the meta-release.

  • 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 Start following the scope definitions of Commonalities and ICM and assess impact on API version
  • 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
    • Assess final impact of final release-candidates of Commonalities and ICM scope on API(s)
    • 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)releases
    • 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

...