Spring25 - M3 Milestone - Prepare r2.1

[jgarciahospital]

What type of PR is this?

• documentation
• subproject management

What this PR does / why we need it:

Create rc-1 with r2.1 version of Population Density Data API for spring25 meta-release

Which issue(s) this PR fixes:

Fixes #48

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	2		0	0.02s
✅ OPENAPI	spectral	1		0	1.76s
✅ REPOSITORY	git_diff	yes		no	0.03s
✅ REPOSITORY	secretlint	yes		no	0.73s
✅ YAML	yamllint	1		0	0.49s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by

[jgarciahospital]

Fixing small typos on errors, and including adaption of ICM description as in https://github.com/camaraproject/IdentityAndConsentManagement/blob/r2.2/documentation/CAMARA-API-access-and-user-consent.md#mandatory-template-for-infodescription-in-camara-api-specs

[hdamker]

Very few comments on the release related files, see below, they are looking good.

The challenge is the missing update of the .feature file, which is mandatory for a release candidate version and with that for M3. The intention of the release candidate is that someone can take the pre-release, implement the API definition and then test it with the test definitions in the pre-release. Without the test definitions it would be an alpha version of the API.

Given the overall shape of the API and that the changes of the feature file are already prepared, we should find an exceptional way to get the updated API into the meta-release. Preferred would be that the updated .feature gets merged before this release PR to have a consistent release candidate.

[jgarciahospital]

@hdamker thanks for the review, comments are included and PR of Test Plan is merged as well for solving all the pending topics.

[hdamker]

Assuming that the API is already aligned with r2.2. of Commonalities and ICM (at least my impression), please state so and we done here! Great work!

[hdamker]

Add here and in the next line either r2.1 or r2.2 (rc) as reference information for the release of Commonalities your API is aligned with.

[jgarciahospital]

fixed

[bigludo7]

Thanks @jgarciahospital 👍

[jgarciahospital]

Typos of version in .freature file solved and reference to r2.2 commonalities and ICM -rc.1 included

[hdamker]

The version of the API definition file need to be updated here in the release PR (in main it is still wip which is correct, but not for the release).

Plus one minor other change.

[jgarciahospital]

The version of the API definition file need to be updated here in the release PR (in main it is still wip which is correct, but not for the release).

Plus one minor other change.

rc.1 included in API definition file.

[hdamker]

Guess we are now there :-)

Looks good from release management perspective.