Agenda

Minutes

Action items review

No actions on Release Management Working Group - CAMARA Project - CAMARA Projecttanja to …
raise an issue in Commonalities (Rafal Artych ) to discuss if it is a breaking change to change error codes (add, update, remove) as we need the guidance
- From TSC on Dec 19th: “APIs should strictly apply semantic versioning regarding breaking changes. Any change that may break an implementation (e.g. changes in error response codes) should be considered as a breaking change” - Tanja de Groot to check if documentation needs to be updated (github & wiki)
- More detailed discussion:
  - error codes changes are considered breaking changes IF they require update of test definitions
  - some cases are not testable (e.g; wrong method) so there are no test definitions
  - removal of information from the API spec that does not impact the API client is not considered a breaking change
linting rule for checking mandatory error codes- Rfal is checking

Spring25 meta-release

General

Missing

Put an issue in the 2 sub projects to raise the question if they want to be ârt of Spring25 Tanja de Groot

M3

API release PRs for M3 are to be done ASAP. propose to send email to codeowners after this call to
- update the API release trackers: completion of fields + addition of “New” filed in the table.
- reminder to create the release PR and invite release-management-maintainers for reviewing it
Cut-off date for API release PR review request is 2025-01-17

Issues review

General issues

discussion on asset versioning to be completed: all assets to be handle similar to API files Tanja de Groot to update the description
future evolution to use version numbers inside all assets including documents, rather than the VERSION file should be done latest by stable version of assets. Issue to be created. yjis issue to be closed.

Release PRs review issues

AOB