Prepare release r1.2

[hdamker]

What type of PR is this?

Add one of the following kinds:

• documentation
• subproject management

What this PR does / why we need it:

This is the release PR for r1.2.

• Update of CHANGELOG.md

  • Moved new release to top
  • Applied the CHANGELOG.md template to r1.2
  • Replaced links to issues with links to PRs
  • Removed formal changes which are not relevant for API users

• Update Call_Forwarding_Signal.yaml

  • Removed comments from Design Guidelines (not meant to be in the YAML)
  • Updated x-camara-commonalities to the current available version
  • Updated version and server url for rc.2
  • Aligned server URL description with latest Commonalities guideline

• Deleted obsolete README.md in API_Definitions

• Cosmetic change within call-forwarding-signal-API-Readiness-Checklistst.md

Which issue(s) this PR fixes:

Fixes #72 #90

Special notes for reviewers:

The PR should be merged only after all issues within scope of #72 are resolved (especially #90) and after the PR got an approval by one of @camaraproject/release-management_maintainers. The merge commit of this PR will get tagged as the release r1.2.

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	2		0	0.03s
✅ OPENAPI	spectral	1		0	1.69s
✅ REPOSITORY	git_diff	yes		no	0.01s
✅ REPOSITORY	secretlint	yes		no	0.72s
✅ YAML	yamllint	1		0	0.33s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by

[FabrizioMoggio]

@hdamker Just one question about this sentence:

"Special notes for reviewers:
The PR should be merged only after all issues within scope of #72 are resolved (especially #90) and after the PR got an approval by one of @camaraproject/release-management_maintainers. The merge commit of this PR will get tagged as the release r1.2."

and especially on this section:

"The merge commit of this PR will get tagged as the release r1.2."

My problem is that in this PR the version is still: wip. I can not create a Release Tag.

In my understanding the sequence is:

1. update your commit with the requested modifications (e.g. the Auth section text). The YAML still has version: wip
2. review and approve the PR by coworkers and release-management_maintainers. Still wip
3. merge the PR
4. create a new PR with just one modification, the version: v0.2.0-rc.2
5. approve the PR
6. merge the PR
7. create the Release Tag

is this sequence correct?

[FabrizioMoggio]

LGTM

[hdamker]

@FabrizioMoggio You have already seen by 0b0b2f3 that I just missed to change the version: wip.

My intention was:

In my understanding the sequence is:

1. update your commit with the requested modifications (e.g. the Auth section text). The YAML still has version: wip

The change of the Auth section could have done also in a dedicated PR for the issue (which would have been merged before this one here). But I'm also fine with your commit 3b72d16 here. I updated the PR description ("Fixes ...") and the CHANGELOG.md.

2. review and approve the PR by coworkers and release-management_maintainers. Still wip

Yes, and this is the release PR, hence it does the change to v0.2.0-rc.2

3. merge the PR
   > 4. create a new PR with just one modification, the version: v0.2.0-rc.2
   > 5. approve the PR
   > 6. merge the PR
4. create the Release Tag

[FabrizioMoggio]

OK

[FabrizioMoggio]

I think that everything is fixed. Waiting for a final approval by @camaraproject/release-management_maintainers before merging.

[chinaunicomyangfan]

LGTM

[rartych]

LGTM

[hdamker]

I think that everything is fixed. Waiting for a final approval by @camaraproject/release-management_maintainers before merging.

@FabrizioMoggio You are good to go ... I just asked @rartych for final view on the PR from release management perspective (as I didn't wanted to approve my own PR).