my-api v0.11.0

Meta-release	Fall24
API name	my-api
Group	N/A
Repository	QualityOnDemand
Target version	0.11.0
Target scope	QualityOnDemand/issues/284
Target maturity	initial
M3 date	2024-06-15
M4 date	2024-08-31
API version	0.10.1
pre-release tag	QualityOnDemand/releases/tag/r1.22
M5 date	yyyy-mm-dd + <shortened link to PR for public API version>
public-release tag	<shortened release tag link>
Comments
Contacts	@ name1, @ name2

API release checklist

Nr	API release assets	alpha	release-candidate	public-release
				initial	stable
1	API definition	Y	Y	Y	Y
2	Application of design guidelines from Commonalities	N	Y	Y	Y
3	Application of profile guidelines from ICM	N	Y	Y	Y
4	API versioning conventions followed	Y	Y	Y	Y
5	API release numbering conventions followed	Y	Y	Y	Y
6	Linting rules enabled	Y	Y	Y	Y
7	Protected branches enabled	Y	Y	Y	Y
8	API documentation	Y	Y	Y	Y
9	Maintainers doc (from at least 3 distinct companies)	Y	Y	Y	Y
10	Codeowners doc (from at least 3 distinct companies)	Y	Y	Y	Y
11	Release notes according to template	Y	Y	Y	Y
12	User stories	Y	Y	Y	Y
13a	Sunny day API test cases and documentation	N	Y	Y	Y
13b	Full set of API test cases and documentation	N	N	Y	Y
14	Test results (API test cases passed)	N	Y	Y	Y
15	Release-candidate API version tested in at least 2 operator implementations	N	N	Y	Y
16	initial public-release API version certified and launched in at least 2 operators is needed to become stable	N	N	N	Y

To be part of a meta-release, minimally the initial release assets need to be provided.

Add any other useful information about the status of the release here.