Release 0.3.0-rc.1

[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 first release-candidate for Carrier Billing APIs Family

This first release candidate r0.3.0-rc.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:

N/A

Changelog input

 Carrier Billing Release 0.4.0-rc.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.04s
✅ REPOSITORY	git_diff	yes		no	0.05s
✅ REPOSITORY	secretlint	yes		no	1.07s
✅ YAML	yamllint	2		0	0.86s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by

[rartych]

@PedroDiez Please note that Release Management decided on decoupling of release numbering from API version numbering.:
https://wiki.camaraproject.org/display/CAM/API+Release+Process#APIReleaseProcess-APIreleasenumbering

Please look also at: CHANGELOG_TEMPLATE.md and CHANGELOG_EXAMPLE.md

[PedroDiez]

@PedroDiez Please note that Release Management decided on decoupling of release numbering from API version numbering.: https://wiki.camaraproject.org/display/CAM/API+Release+Process#APIReleaseProcess-APIreleasenumbering

Please look also at: [CHANGELOG_TEMPLATE.md](https://github.com/camaraproject/ReleaseManagement/blob/main /documentation/CHANGELOG_TEMPLATE.md) and CHANGELOG_EXAMPLE.md

Many thanks Rafal! I will check this accordingly

[hdamker]

@PedroDiez Should I delete this (protected) branch (to clean up)? BTW: only branches with the pattern "*release*" are protected ... something which we will not use anymore going forward.

[PedroDiez]

Should I delete this (protected) branch (to clean up)? BTW: only branches with the pattern "release" are protected ... something which we will not use anymore going forward.

Thanks Herbert, I think it is not required. No blocker for the WG activity. And yes, after checking with Rafal few weeks ago release branches will no longer be using.

[hdamker]

@PedroDiez I renamed the branch to obsolete-0.3.0-rc.1 and deleted it, so that no-one is confused by it. It would btw make sense to clean-up the about 80 branches within the repository ... normally most of them should have been in personal forks as we are following the "fork and pull" model (cf. https://github.com/camaraproject/Governance/blob/main/CONTRIBUTING.md). But first the release, then the clean-up.

[PedroDiez]

Ok take note of this task to be done in future