Skip to content

Prepare maintenance release r2.3#91

Open
fernandopradocabrillo wants to merge 1 commit into
camaraproject:maintenance-r2from
fernandopradocabrillo:prepare-maintenance-release
Open

Prepare maintenance release r2.3#91
fernandopradocabrillo wants to merge 1 commit into
camaraproject:maintenance-r2from
fernandopradocabrillo:prepare-maintenance-release

Conversation

@fernandopradocabrillo

Copy link
Copy Markdown
Contributor

Update CHANGELOG.md, README.md and API Readiness Checklist to reflect the new maintenance release tag r2.3, which fixes test scenario error codes and typos compared to r2.2.

What type of PR is this?

  • subproject management

What this PR does / why we need it:

Prepares the maintenance release r2.3 by updating all release version references from r2.2 to r2.3. The API definition (device-swap v0.2.0) is unchanged; this release contains only test definition fixes introduced in PR #87.

Which issue(s) this PR fixes:

Fixes #84

Special notes for reviewers:

The API YAML spec is not modified. The only functional changes in this release line are in the test feature files (already merged via PR #87): error code NOT_SUPPORTED corrected to SERVICE_NOT_APPLICABLE and several typos fixed in scenario descriptions.

Changelog input

Update CHANGELOG.md, README.md and API Readiness Checklist to reflect
the new maintenance release tag r2.3, which fixes test scenario error
codes and typos compared to r2.2.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@fernandopradocabrillo

Copy link
Copy Markdown
Contributor Author

Hi @hdamker! this one is for the maintenance release, I hope I covered everything, it's been a while since the last one I did 😄 if something is missing we can blame claude 👀

@hdamker

hdamker commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

I would recommend to change the API version to 0.2.1:

  • to indicate the patch ... currently the CHANGELOG reads odd, same version but changes
  • as the test definition is part of the API contract (defining the behavior) and at least implementors need to be aware that there were changes. If they see exactly the same version they would not expect any changes
  • the version is also used in the test definition files and should be not the same as in r2.2 (Feature: CAMARA Device Swap API, 0.2.0 - Operation checkDeviceSwap)

The server URL will be unchanged (v0.2), so clients are not impacted as long as the changes in test definition changes do not imply a client visible behavior change.

@bigludo7 bigludo7 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants