Release 0.2.0-rc.1

[jpengar]

What type of PR is this?

• subproject management

What this PR does / why we need it:

This is "Release PR" for ICM Release 0.2.0-rc.1

Which issue(s) this PR fixes:

Related to #146

Special notes for reviewers:

• The team agreed to proceed with a release candidate directly, bypassing the alpha release, given the stability and closed scope of the current state. See https://wiki.camaraproject.org/x/JYDcAQ for further details.
• README.md - with the existing format in ICM there is no need to change anything.
• CAMARA-AuthN-AuthZ-Concept.md is DEPRECATED and needs to be removed, but we should do it for the public release I think, not now for this release candidate "pre-release" (to avoid "breaking" the main branch now).
• References in the released documents should always be links to a released version, not to the main branch. If the documents are released together, the links need to be updated at least within the release PR. But, same as previous point, we should do it for the public release, I think, and not now for this release candidate "pre-release" (to avoid "breaking" the main branch now).
• CHANGELOG.md - Only the CHANGELOG file needs to be updated in the pre-release for now. Added all changes from the previous public release v0.1.0.

NEXT STEPS (edited by @hdamker):

• Merge this PR when ready.
• Merge Proposed text on network-based authentication #173 as agreed in the June 19 WG meeting call. → UPDATE (21/06): DONE
  - Create release v0.2.0 branch: release-0.2.0-rc
• Create a release v0.2.0-rc.1 tag for the latest commit.
• Create pre-release v0.2.0-rc.1 in the github project (copy the section from CHANGELOG.md into the description)

NOTE: I will be on vacation for the next two weeks, I will need @AxelNennker, @sebdewet or other volunteers to continue this work for me. My goal is to merge this PR before I leave :) (fingercross)

Changelog input

ICM Release 0.2.0-rc.1

Additional documentation

https://wiki.camaraproject.org/display/CAM/Meta-release+Process#MetareleaseProcess-Milestoneactivities
https://wiki.camaraproject.org/display/CAM/Meta-release+Fall24

[diegogonmar]

LGTM

[hdamker]

The PR looks good for me. Just suggest the change of all links:

• the tag should be v0.2.0-rc.1 instead of v0.2.0-rc
• we dropped the creation of "release" branches (especially for pre-releases), instead the links should go directly to the tag within the blob/tree.

Fingers crossed that my suggested links are correct after the tag v0.2.0-rc.1 is created ...

[diegogonmar]

LGTM. Thanks for the adjusts

[hdamker]

@AxelNennker
a) there are three "hidden" suggestions in my review to be committed to update the remaining links
b) I've updated the description of the PR slightly to align it with the versioning and release process guidelines

[tanjadegroot]

For the release process, please add @camaraproject/TSC_participants to the reviewers of this PR.

[sebdewet]

LGTM

[AxelNennker]

@hdamker fixed the links and a accepted the suggestions.
Merging soon

[hdamker]

Thanks a lot @jpengar and @AxelNennker for the pull request. It looks good for me.

Within TSC today (draft minutes) we have decided to keep the release candidate PRs for Commonalities and ICM open until Wednesday, July 10th, for a final review including the TSC participants. So please wait with the merge until then.

[shilpa-padgaonkar]

/LGTM

[rartych]

It can be merged now.

[hdamker]

@AxelNennker @jpengar Can one of you please merge this PR and create the pre-release in GitHub before today's AHC on 16:00? If you can't for some reason I offer to take it.

[jpengar]

@AxelNennker @jpengar Can one of you please merge this PR and create the pre-release in GitHub before today's AHC on 16:00? If you can't for some reason I offer to take it.

@hdamker @AxelNennker @sebdewet Done. Please take a look to double check that everything is ok.

[hdamker]

@jpengar Thanks! Looks good to me. I would just recommend to update the README.md and mention there the release candidate explicitly, maybe even replacing the link to "latest public release" v0.1.0, as now the v0.2.0-rc.1 is more important.

[jpengar]

@jpengar Thanks! Looks good to me. I would just recommend to update the README.md and mention there the release candidate explicitly, maybe even replacing the link to "latest public release" v0.1.0, as now the v0.2.0-rc.1 is more important.

@hdamker @AxelNennker @sebdewet #179 please review.