This page is to prepare the messages for the announcement of milestones or other events from the release management team.
Spring25
2024-10-09: Spring25 meta-release: M0 announcement (all@lists.camaraproject.org)
We are pleased to announce that the TSC has declared the kick-off (M0) of the Spring25 meta-release in their October 3rd meeting.
The meta-release plan can be found here: Meta-release Spring25.
For M1 (Oct 31st), the Commonalities and Identity & Consent Management teams are working hard on their scope definitions:
The set of related PRs are under preparation: critical PRs will be available by Oct 15th and other PRs by Oct 31st.
Exceptionally, no pre-releases will be available yet for M1, so Sub-Project teams are asked to review and comment the PRs and start taking them into account as of M1.
For questions or comments, please use the GitHub issues, the FAQ or email the wg-release-management@lists.camaraproject.org.
All teams off to Spring25 😊
The CAMARA Release Management team
Fall24
2024-07-19: M3 milestone - new date: 2024-07-26 & preparation hints (to rm mailing list)
Dear all,
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.
Other HINTS: (see API guidelines section 11.1)
check that your servers object in the yaml looks as follows:
servers:
- url: '{apiRoot}/yourapiname/v0.yrc1
...
or v1rc1'
variables:
apiRoot:
default: http://localhost:9091
description: API root, defined by the service provider, e.g. `api.example.com` or `api.example.com/somepath`
add the following in the yaml in the info object: x-camara-commonalities: 0.4.0
example:
info:
title: One Time Password SMS
...
x-camara-commonalities: 0.4.0
termsOfService: http://example.com/terms/
contact:
name: API Support
url: http://www.example.com/support
email: support@example.com
license:
name: Apache 2.0
...
The links to the latter 2, and more generally on the API release process, are on the RM wiki and in GitHub.
Thanks !
The CAMARA Release Management team
...
Please review the following 2 release PRs in preparation of the M2 milestone:
Commonalities: Release 0.4.0-rc.1 by rartych · Pull Request #240 · camaraproject/Commonalities (github.com)
Identity and Consent Management: Release 0.2.0-rc.1 by jpengar · Pull Request #177 · camaraproject/IdentityAndConsentManagement (github.com)
Thanks !
The CAMARA Release Management team
...
This email is to announce
the M0 (kick-off) of the Fall24 meta-release which was approved by the TSC on April 18th
the pre-M1/M2 announcement for Commonalities and Identity and Consent Management (ICM)
Fall24 Commonalities & Identity and Consent Management
The scope issues that describe the content for the meta-release are available here:
Commonalities: Commonalities release 0.4.0 scope · Issue #175
Identity and Consent Management: Create ICM Release Plan · Issue #146
alpha releases for M1:
Commonalities: published its alpha release: Release v0.4.0-alpha.1 · Commonalities
Identity and Consent Management: will do no alpha release, and go directly to the release-candidate.
the release PRs for release-candidates for M2.
The meta-release can be found here: Meta-release Fall24.
All interested API Sub Projects are asked to prepareprepare their release-candidate(s) API versions for the M3 of the Fall24 meta-release.
To do this please
create
...
...
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
Have fun for Fall24 
The Release Management team
...