Release r1.1 (Release Candidate)

[PedroDiez]

What type of PR is this?

Add one of the following kinds:

• documentation
• subproject management

What this PR does / why we need it:

Generation of release r1.1 (release candidate) for Carrier Billing APIs Family

This release candidate r1.1 contains the definition and documentation of

• Carrier Billing v0.3.0-rc.1
• Carrier Billing Refund v0.1.0-rc.1

The API definition(s) are based on

• Commonalities v0.4.0
• Identity and Consent Management v0.2.0

Which issue(s) this PR fixes:

Fixes #164

Special notes for reviewers:

• Follow Up of Release 0.3.0-rc.1 #165. Closed as i was not able to make more commits as protected branch
• Follow Guideline Recommendations provided by Rafal
• Adapt recent updates in "# Authorization and authentication" section from I&CM - Replace link into main branch of Identity and Consent Management within "Authorization and authentication" text template IdentityAndConsentManagement#186
• Remove "termsOfService" and "contact" from OAS info object

Changelog input

 Carrier Billing Release r1.1

Additional documentation

N/A

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	2		0	0.03s
✅ OPENAPI	spectral	2		0	4.05s
✅ REPOSITORY	git_diff	yes		no	0.05s
✅ REPOSITORY	secretlint	yes		no	0.98s
✅ YAML	yamllint	2		0	0.85s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by

[bigludo7]

LGTM

[rartych]

LGTM

[hdamker]

@PedroDiez @rartych The PR seems to be in quite good shape. Is there anything open to be done before the release candidate can be created? Also #166 seem to be ready?

I have proactively created camaraproject/ReleaseManagement#70 for the review through Release Management, but please add @camaraproject/release-management_maintainers as reviewer if you want to get the review and approval by them.

[PedroDiez]

@PedroDiez @rartych The PR seems to be in quite good shape. Is there anything open to be done before the release candidate can be created? Also #166 seem to be ready?

I have proactively created camaraproject/ReleaseManagement#70 for the review through Release Management, but please add @camaraproject/release-management_maintainers as reviewer if you want to get the review and approval by them.

Hi @hdamker! Yes it is ready to be merged.
Anycase let's follow the "formal" procedure. Have been added RM maintainers to wait for their approval. Indeed it was a doubt that I was to query in today's CB meeting, 100% clear with your comment. Many thanks for helping on this!

[rartych]

To be formally correct and following the note below the table:

"tbd" is in case an alpha or release-candidate API version does not yet provide all mandatory assets for the release

the status in 7th row of Readiness checklists in RC.1 needs to be changed to:

Nr	API release assets	alpha	release-candidate	initial public	stable public	Status	Comments
7	Basic API test cases & documentation	O	M	M	M	tbd	link

[rartych]

Release PR approved - on behalf of Release Management

[hdamker]

@PedroDiez @rartych One small final point spotted ... will support with the merge afterwards.

[PedroDiez]

@PedroDiez @rartych One small final point spotted ... will support with the merge afterwards.

Thanks for the review Herbert

[hdamker]

Merging on behalf of Codeowners

[PedroDiez]

Many thanks @hdamker!