Update release-plan.yaml for r3.2

[Masa8106]

What type of PR is this?

• subproject management

What this PR does / why we need it:

• Update release-plan.yaml for the Number Recycling 2nd release candidate preparation.

Which issue(s) this PR fixes:

N/A - no upstream issue.

Special notes for reviewers:

Align ReleasePlan yaml file with new Commonalities 4.4 version

target_release_tag: r3.2
commonalities_release: r4.4
target_api_version to 0.3.0

Changelog input

None

Additional documentation

None

[albertoramosmonagas]

A question, with the new release, do we need to update the API version? @eric-murray @Masa8106? For example, as is the case with the “commonalities” patch, we need to change from 0.3.0 to 0.3.1?

[Masa8106]

@albertoramosmonagas, as far as I see a case of QoD API, The versions of 1st release candidate and 2nd release candidate (before public release) are the same. So I didn't try to change this time.

I guess we need to change PATCH version after public release.
In "commonalities" case, r4.3 is the Singal26 public release and r4.4 is the Signal26 patch release.
https://github.com/camaraproject/Commonalities/blob/main/documentation/CAMARA-API-Design-Guide.md#7-versioning

If my understandig is wrong, please let me know.

[albertoramosmonagas]

@albertoramosmonagas, as far as I see a case of QoD API, The versions of 1st release candidate and 2nd release candidate (before public release) are the same. So I didn't try to change this time.

I guess we need to change PATCH version after public release. In "commonalities" case, r4.3 is the Singal26 public release and r4.4 is the Signal26 patch release. https://github.com/camaraproject/Commonalities/blob/main/documentation/CAMARA-API-Design-Guide.md#7-versioning

If my understandig is wrong, please let me know.

To be honest, I have no idea. For example, with Tenure, I did it this way: if the previous version was 0.3.0, when a new release comes out, it goes to 0.3.1 because the commonalities have changed from r4.3 to r4.4, and the release tag also changes, but I really have no idea. That was my first thought when I did it

[hdamker]

@Masa8106 @albertoramosmonagas Please have a look on my comment camaraproject/QoSBooking#142 (comment) for the same question.

The PR is correct as is ... the automation will create the correct 0.3.0-rc.2 version at snapshot time, in line with the version guidelines in the Design Guide.