This page is to prepare the messages for the announcement of milestones or other events from the release management team.
...
2024-07-19: M3 milestone - new date: 2024-07-26 & preparation hints (to rm mailing list)
Dear all,Please be reminded
In the light of the
...
upcoming M3 milestone
...
, please find the following point to get prepared
...
:
the TSC has shifted the M3 date to 2024-07-26,but earlier is very welcome- at this date it is sufficient to have the release PR forthe API release-candidate.
- please put the link to the release PR in the (pre)-release tag field on the API release tracker when your PR is ready for review
- in this release PR you need to include:
- any updates to the readme.md as needed
- the update of the changelog.md file
- see example here: ReleaseManagement/documentation/CHANGELOG_EXAMPLE.md
HINT: create a "draft release" with GitHub to see the relevant changes since the previous version and select relevant PRs, reformulate as needed and sort them into the categories of the changelog.
- the update of the yaml file with the concerned API version and URL
A reminder that the API version (x-y-z-rc.1) is different from the release number of the pre-release (which will be r1.1).
- the update of the API readiness checklist with all required content for the release-candidate
- exceptionally, although the checklist mandates to provide the basic test cases with the release-candidate, for this first meta-release, the Sub Projects are allowed to delay these to M4. However the earlier the test cases are provided, the longer the time to actuall test any available API implementation. Please use the comment field in the checklist to indicate the delay if any. M3 will not be blocked on this point.
- do not use release branches anymore: all releases are to happen using the GitHub release feature from the main branch and setting release tags on the main branch. If this is an issue for M3, this can be resolved for M4.
- please notify the Release Management team to review the PR by adding https://github.com/orgs/camaraproject/teams/release-management_maintainers as reviewers to the release PR.
...
- create the API release tracker for the API version(s) planned for the Fall24 meta-release (see the wiki page for more info)
- subscribe your API contacts to the wg-release-management@lists.camaraproject.org for further announcements
- start the activities described for the API Sub Projects here: Meta-release Process
- develop the API(s) and check alignment with the Commonalities and ICM scope issue / release PR
- announce API progress on the API's release tracker each time an API version (with its release assets according to the checklist) is made available
For questions or comments, please use the GitHub issues, the FAQ or email the wg-release-management@lists.camaraproject.org
...