Update Release Plan according to Sync26

[albertoramosmonagas]

What type of PR is this?

Add one of the following kinds:

• subproject management

What this PR does / why we need it:

This PR updates the repository release plan for the Sync26 meta-release.

It aligns the release-plan.yaml with the next CAMARA release cycle by:

• setting the repository participation to Sync26
• updating the planned release information for this repository
• aligning the declared dependency releases with the target cycle

This is needed so the repository is correctly tracked by the Release Management automation and remains consistent with the current CAMARA release planning process.

Which issue(s) this PR fixes:

Fixes #109

Special notes for reviewers:

Please review this PR from a release planning perspective.

This change does not modify API behavior or implementation. It only updates the repository release declaration so it is correctly aligned with the Sync26 planning cycle and Release Management tooling.

Changelog input

 release-note
Update release-plan.yaml to align this repository with the Sync26 meta-release planning cycle.

Additional documentation

This section can be blank.

docs

[albertoramosmonagas]

@camaraproject/population-density-data_codeowners I've created the post for integrating the API for sync26; I've set it to draft because I've included the public version of the commonalities, which still needs to be ready.

[hdamker]

@albertoramosmonagas you might want to consider an alpha release together with the Commonalities rc2, also to support he validation of this release candidate (at least that is the idea of the rc phase). But also ok to wait for r4.3

[albertoramosmonagas]

u might want to consider an alpha release together with the Commonalities rc2, also to support he validation of this release candidate (at least that is the idea of the rc phase). But also ok to wait for r4.3

Thanks @hdamker, I’ll bring this up in our upcoming meetings for both Predictive and Population, but I thought the alpha version was only required for those APIs that were part of their first meta-release.

[hdamker]

u might want to consider an alpha release together with the Commonalities rc2, also to support he validation of this release candidate (at least that is the idea of the rc phase). But also ok to wait for r4.3

Thanks @hdamker, I’ll bring this up in our upcoming meetings for both Predictive and Population, but I thought the alpha version was only required for those APIs that were part of their first meta-release.

You are right, not required, as I wrote. But the new process, refs/bundling, and the new rules in Commonalities are together a lot of changes ... so it makes sense to "exercise" with an alpha release.