Pre-release r1.1 of v0.1.0-rc.1

[fernandopradocabrillo]

What type of PR is this?

Add one of the following kinds:

• subproject management

What this PR does / why we need it:

Include neccesary documentation to create the first public pre-release r1.1

Which issue(s) this PR fixes:

Fixes #17
Fixes #19

[hdamker]

@FabrizioMoggio Thanks, I will create the review issue within Release Management.

And: I know it is confusing, but it is either a pre-release (if the the API version is an alpha or rc version) or a release of a public API version ... there is no such thing as a public pre-release. I edited the title of the PR accordingly.

[hdamker]

Looks generally good from Release Management point of view, but the links within CHANGELOG need to be corrected.

[hdamker]

A question about the version and the aim for Spring25: The release tracker for 0.1.0 is stating that the version 0.1.0 is targeted for Spring25 meta-release. For that meta-release the API should be based on Commonalities 0.5.0 (e.g. some changes to error schema) and you will have the public release around March 2025.

There two options which come to my mind (there might be others):

• doing now soon a public release of 0.1.0 outside of meta-release cycle and doing the adaptions for Spring25 in a 0.2.0
• releasing now an alpha version of 0.1.0 and doing the adaptions to Commonalities 0.5.0 until the release candidate

@fernandopradocabrillo Would be great to share your plan towards the Spring25 meta-release.

[fernandopradocabrillo]

A question about the version and the aim for Spring25: The release tracker for 0.1.0 is stating that the version 0.1.0 is targeted for Spring25 meta-release. For that meta-release the API should be based on Commonalities 0.5.0 (e.g. some changes to error schema) and you will have the public release around March 2025.

There two options which come to my mind (there might be others):

• doing now soon a public release of 0.1.0 outside of meta-release cycle and doing the adaptions for Spring25 in a 0.2.0
• releasing now an alpha version of 0.1.0 and doing the adaptions to Commonalities 0.5.0 until the release candidate

@fernandopradocabrillo Would be great to share your plan towards the Spring25 meta-release.

Hi @hdamker, you are right, I have to update the release tracker to v0.2.0.

The idea is to publish a first version aligned with Fall24 and the update the spec and align with Spring25 for a v0.2.0. At least in TEF we need an official version aligned with current agreements before going for the new one. I though I could have it before, but the WG is a bit short-staffed so it takes time 😄

Thanks for pointing it out, I'll update the release tracker and proceed with the updates once I have the release created here. If possible, before the M3 due date.

[hdamker]

I'll update the release tracker and proceed with the updates once I have the release created here. If possible, before the M3 due date.

Please keep the release tracker for 0.1.0, we are tracking them also here. I've updated the release tracker accordingly. For 0.2.0 please create an additional release tracker.

[hdamker]

LGTM - you are good to go as soon as there is a approval for the latest change from a @camaraproject/location-insights_codeowners

[FabrizioMoggio]

LGTM :-)