Release plan for r2.1

[hubertp-ericsson]

What type of PR is this?

Add one of the following kinds:

• subproject management

What this PR does / why we need it:

This PR is a first stab at the release plan for r2.1.

Which issue(s) this PR fixes:

Fixes #

Special notes for reviewers:

Changelog input

 release-note

Additional documentation

This section can be blank.

docs

[hdamker]

@hubertp-ericsson please merge #101 first - with that the push to release-plan.yaml will trigger the Release Automation workflow.

[tlohmar]

It might be better to target a release-candidate version, instead of an alpha version. We can have multiple release-candidates.

According to CAMARA API releases

• before M3, release (optionally) one or more alpha API versions as needed
• to reach M3, release the first release-candidate API version:
  • the release-candidate implements the scope of the target public API version.
  • this pre-release is agreed to be ready for API implementation and functional testing.
  • it is aligned with the alpha release of Commonalities and ICM for the meta-release (M1).
  • it includes all required API release assets as defined in the API Readiness Checklist for release candidate API versions.

[tanjadegroot]

It might be better to target a release-candidate version, instead of an alpha version. We can have multiple release-candidates.

According to CAMARA API releases

• before M3, release (optionally) one or more alpha API versions as needed

• to reach M3, release the first release-candidate API version:

  • the release-candidate implements the scope of the target public API version.
  • this pre-release is agreed to be ready for API implementation and functional testing.
  • it is aligned with the alpha release of Commonalities and ICM for the meta-release (M1).
  • it includes all required API release assets as defined in the API Readiness Checklist for release candidate API versions.

It was recommended to do an alpha release first to introduce of the automated release process as per Herbert's indications. After this, doing releases will be really easy and you can concentrate on content.
However you can also do this through an rc, so ok if you want to do that.

BTW The up-to-date documentation for (automated) API release is now in GitHub here.

[tlohmar]

Looks good. We should create the Release-Candidate as next release

[hdamker]

It is the intention to make the independent release still against Fall25 Commonalities, right? Then these lines are correct.

[tlohmar]

It is the intention to make the independent release still against Fall25 Commonalities, right? Then these lines are correct.

Yes, we plan to bump to the next commonalities release with the next release, i.e. when getting closer to Sync26