update the release-plan file for the Sync26 release.

[ChinaUnicomXiaoDongrui]

Our APIs（eSimRemoteManagement） is expected to be public released in Sync26. So we update the release-plan file as required

[ChinaUnicomXiaoDongrui]

@hdamker @tanjadegroot hello, we hope to release it in the Sync 26 phase. According to the notice, we need to complete the update of the release-plan file by June 18th. Please help us check if it is correct. Thank you. Then I will inform our owner to review and merge it @SentianSun

[hdamker]

@hdamker @tanjadegroot hello, we hope to release it in the Sync 26 phase. According to the notice, we need to complete the update of the release-plan file by June 18th. Please help us check if it is correct. Thank you. Then I will inform our owner to review and merge it @SentianSun

@ChinaUnicomXiaoDongrui

I'm sorry, but according to the TSC decision in its 2026-03-19 meeting please proceed with the independent release cycle and keep from this PR only the change of the API name:

• Every new (initial) API will start with an independent release cycle, and should do a first alpha release.
• Independent API releases are reviewed by Release Management just like any meta-release API. Focus for alpha release reviews is on syntax issues as (raised by validation); release candidates should address semantics review comments such as RESTful design comments.
• This is to avoid meta-releases being blocked by too long reviews, and allowing teams to get familiar with the CAMARA guidelines.

If the API has reached the needed maturity for a meta-release participation I can see a potential TSC exception at a later point of time to take the API into the meta-release. But first we would need to see the API, the compliance with CAMARA guidelines, quality, and fit into the CAMARA portfolio. That is what a sandbox is meant for and why we created it 6 months ago.

[ChinaUnicomXiaoDongrui]

@hdamker Thank you for your reply. What you mean is that announcing participation in Sync26 before June 18th (by updating the release-plan file) refers to the apis that have completed meta-release or independent version release. However, for those who have not completed the independent version release, after the independent version is completed(for instance, I completed the independent release in July), can they catch up with Sync26 for the meta-release. I hope to receive your reply and assistance. Thank you

[hdamker]

@hdamker Thank you for your reply. What you mean is that announcing participation in Sync26 before June 18th (by updating the release-plan file) refers to the apis that have completed meta-release or independent version release. However, for those who have not completed the independent version release, after the independent version is completed(for instance, I completed the independent release in July), can they catch up with Sync26 for the meta-release. I hope to receive your reply and assistance. Thank you

Exactly that was I meant with "potential TSC exception at a later point of time to take the API into the meta-release [Sync26]". But until there is a CAMARA compliant, reviewed initial API version the discussion is theoretical - I would recommend to focus on this first.

[ChinaUnicomXiaoDongrui]

@hdamker Thank you for your reply. What you mean is that announcing participation in Sync26 before June 18th (by updating the release-plan file) refers to the apis that have completed meta-release or independent version release. However, for those who have not completed the independent version release, after the independent version is completed(for instance, I completed the independent release in July), can they catch up with Sync26 for the meta-release. I hope to receive your reply and assistance. Thank you

Exactly that was I meant with "potential TSC exception at a later point of time to take the API into the meta-release [Sync26]". But until there is a CAMARA compliant, reviewed initial API version the discussion is theoretical - I would recommend to focus on this first.

@hdamker ok, I see. Thank you for your reply. First of all, we need to complete the release of the independent version. I will close this pr. According to the requirements, we will submit the pr (including the files required for the repository) as soon as possible. What I want to say is, Should the release-plan file (modifying the API name) be updated now or after the pr is submitted or approved

[hdamker]

What I want to say is, Should the release-plan file (modifying the API name) be updated now or after the pr is submitted or approved

Would be good if you merge the PR now with the API name (reverting the two other changes) - with that we can see in https://camaraproject.github.io/ReleaseManagement/progress.html already the right name instead of "place-holder". After you have a YAML file which validates without errors, you can change to alpha instead of draft and also declare the intent of an pre-release-alpha.

[ChinaUnicomXiaoDongrui]

@hdamker Thank you for your guidance. I have recreated the pr and only modified the API name(#15), please help us to review, and I still have two questions :

1. This page(https://camaraproject.github.io/ReleaseManagement/progress.html ) wasn't updated by us, was it?
   2.change to alpha instead of draft and also declare the intent of an pre-release-alpha. Is this to update the release-plan file, or where to operate.