Create ICM Release Plan

[AxelNennker]

Problem description
TSC asked ICM to create a release plan

https://wiki.camaraproject.org/display/CAM/Meta-release+Fall24

Expected action
e.g. Label issues or create a icm-release-plan-document.md

[jpengar]

I think we can use this issue as a way to agree the scope of the release and proceed as done in Commonalities in camaraproject/Commonalities#175 CC @rartych

Some relevant references:
https://wiki.camaraproject.org/display/CAM/CAMARA+Release+Process
https://wiki.camaraproject.org/display/CAM/Releasing+API+versions

[jpengar]

As agreed in the 08/05 WG call, we are using the v0.2-candidate label to mark issues to be addressed in the Fall24 meta-release. A new label ICM-backlog has been created to mark other issues that remain in the WG backlog. So far, the list of issues/PRs to be resolved within Fall24 meta-release are:

• Scope at "API level" feedback from country market implementation #95 >> I think this one could be closed by Camara OIDC profile #121 which removes "API level" scope...
• Claims to be used in oAuth Access tokens/ OIDC Identity tokens #100
• Camara OIDC profile #121
• Proposal to protect the /authorize endpoint for the Authorization Code Flow (Auth Code Flow) - RFC9101 #128
• Inconsistent statements about applicable authorization flows #131
• Management of opt-out with Implicit consent (legitimate Interest) #138
• Add examples for CAMARA Security and Interoperability Profile #143
• CAMARA ICM-examples #148
• "CAMARA-API-access-and-user-consent.md" aligment with last decisions made in profile doc #154
• CAMARA-API-access-and-user-consent.md aligment with last decisions made in profile #155
• Fix statement about "missing sub claim" in case there is no id token #156
• Fix statement about "missing sub claim" in case there is no id token #158
• Explain or remove "3-legged" in CAMARA APIs access and user consent management #159
• Add 3-legged access token definition #162
• Auth code flow update to fix Issue #138 #170

[hdamker]

Added the link to this issue to https://wiki.camaraproject.org/display/CAM/Meta-release+Fall24.
(and took the freedom to replace "tag" with "label" in the above comments).

[jpengar]

Added #154 & #155 to the list of issues/PRs to be resolved within Fall24 meta-release: #146 (comment)

[jpengar]

Added #156, #158 and #159 to the list of issues/PRs to be resolved within Fall24 meta-release: #146 (comment)

[jpengar]

Added #162 which fixed #159 to the list of issues/PRs to be resolved within Fall24 meta-release: #146 (comment)

[jpengar]

Added #170 to the list of issues/PRs to be resolved within Fall24 meta-release: #146 (comment)

[AxelNennker]

I think we need a PR for https://github.com/camaraproject/IdentityAndConsentManagement/blob/main/CHANGELOG.md and document what our documents are etc.
Would @jpengar or @sebdewet please create that PR because I am on vacation starting next Monday.

[jpengar]

If I understand your point correctly, CHANGELOG should be edited as part of the v0.2.0 release (i.e. FAll24 meta-release), as it was when the v0.1.0 release was generated. We can do that during your holidays, no problem.

[jpengar]

Meta-release scope is now 100% covered. Thanks everyone!

[jpengar]

#177 is ready to review for release 0.2.0-rc creation. @AxelNennker @sebdewet @Elisabeth-Ericsson @garciasolero @hdamker @shilpa-padgaonkar @diegogonmar @bigludo7 @mhfoo et all

[jpengar]

#177 is MERGED and v0.2.0-rc.1 created https://github.com/camaraproject/IdentityAndConsentManagement/releases/tag/v0.2.0-rc.1

[jpengar]

#179 README update for v0.2.0-rc.1 pre-release

[AxelNennker]

Create rc.2 with bug fixes.

[hdamker]

Create rc.2 with bug fixes.

One bug which I have introduced is the release tag. It should have r0.2.0-rc.1 instead of v0.2.0-rc.1 (cf camaraproject/ReleaseManagement#41). So let's use the next release candidate and create it correctly as r0.2.0-rc.2.

[jpengar]

Create rc.2 with bug fixes.

One bug which I have introduced is the release tag. It should have r0.2.0-rc.1 instead of v0.2.0-rc.1 (cf camaraproject/ReleaseManagement#41). So let's use the next release candidate and create it correctly as r0.2.0-rc.2.

@hdamker Yes, we discussed this in the last WG call, and we agree to fix it in the next release candidate, expected next Friday. I will add this to the meeting notes for the record: https://wiki.camaraproject.org/display/CAM/2024-07-17+ICM+Minutes

[jpengar]

PR #181 to generate ICM release r0.2.0-rc.2 is ready for review. FYI.
CC @hdamker

So far, the list of issues/PRs to be resolved within release r0.2.0-rc.2 are:

• Fix returned error in authentication code flow #180
• Release r0.2.0-rc.2 #181
• Editorial changes to CAMARA-API-access-and-user-consent.md #183
• Link within mandatory text for all APIs points to main branch - need to be corrected in rc.2 #185
• Replace link into main branch of Identity and Consent Management within "Authorization and authentication" text template #186
• Replace internal links between ICM documents with relative links to stay within the same release tree / fork / release package #187
• Replace internal links between icm documents with relative links #188

[jpengar]

r0.2.0-rc.2 release created https://github.com/camaraproject/IdentityAndConsentManagement/releases/tag/r0.2.0-rc.2

[jpengar]

@camaraproject/release-management_maintainers Should we proceed to create the PR for the public release of 0.2.0 as is being also raised in camaraproject/Commonalities#282??

I would like to discuss how to proceed with creating the ICM public release so that other backlogged PRs can be addressed.

CC @AxelNennker @sebdewet @rartych

[hdamker]

@jpengar sorry for the late answer, it went through the cracks.

We discuss today in Release Management call that Commonalities and ICM should have their PRs for the public releases ready before the TSC on Thursday afternoon. Preferable already with some Codeowner approvals, so that the TSC can "approve" the releases and it can get created (it should be done before the Sub Project are doing their public releases).

As this is more a formal thing I hope that is possible?

If there are later bugfix releases 0.2.x needed, they will done in a maintenance branch which starts in r0.2.0. Which means that after the public release of 0.2.0 end of the week the main branch is free to continue with the work for the next release cycle.

CC @AxelNennker @sebdewet @rartych

[jpengar]

#192 PR for the public release of ICM 0.2.0 is ready for review. @AxelNennker @sebdewet @hdamker @camaraproject/release-management_maintainers

[jpengar]

Public release r0.2.0 is available at https://github.com/camaraproject/IdentityAndConsentManagement/releases/tag/r0.2.0

[AxelNennker]

As per discussion in the wg meeting today