DRAFT FOR REVIEW
...
- the expected alpha, release-candidates and public-release API versions need to be (pre-)released
- minimally an initial public-release need to be provided
- each (pre-)release must provide the required set of API release assets according to the API readiness checklist described below.
- API (pre-)releases are numbered (tagged) using the API release numbering guideline (see below)
Technically, an API release is created using GitHub features:
- A GitHub issue for the release
- A "release PR" for this issue
- If required, a GitHub release package (zip file of the API Sub Project repository)
- A GitHub release tag with the release name rx.y
API release numbering
API release numbers are GitHub tags of the format "rx.y".
...
This section gives the overview of the steps to release an API. more More details can be found in the the API Release Process description.
...