Versions Compared

Old Version 49

changes.mady.by.user Tanja de Groot

Saved on

compared with

New Version 50

changes.mady.by.user Tanja de Groot

Saved on

Key

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

...

The Commonalities and ICM teams shall respectively update the related meta-release page table as follows:

  • The Version (Pre-)Release tag column shall be updated with the latest pre-release version in use by the respective teamstag link to the API version whenever a new pre-release is made available.
  • The actual milestone dates shall be put in the table when the milestone is passedachieved. 
  • The link to the release package shall be added at each version pre-release change, and at M2 (and is the same at M5).
  • When M2 is passed and TSC approval is given, the target public-release version shall be created and the link put in the Version (Pre-)Release package column.

APIs (M0, M3, M4)

API Sub-project teams shall update the table for APIs as follows: 

  • The Version (Pre-)Release tag column shall be updated with the latest pre-release API version in use by the team.
  • The actual milestone dates shall be put in the table when the milestone is passed. 
  • The link to the release package shall be added at each version pre-release change, and minimally at M3, M4, and the final at M5.
  • When M5 is passed, the target public- release API version shall be put in the Version (Pre-)Release tag column.

For sub-projects that contain multiple APIs in separate files,

  • A folder per API shall be created for its development.The meta-release page shall list the individual APIs in the table with the API version considered in the meta-release., ONLY if all APIs are managed under the same version, else a separate API Sub-project shall be created
  • The API version used in the API release asset naming for pre- and public releases include the API name. However, the API OAS definition file only has the semver API version. 

...