camaraproject / DeviceStatus

Repository to describe, develop, document and test the Device Status API family
Apache License 2.0
11 stars 33 forks source link

Prepare release r1.1 #190

Closed akoshunyadi closed 4 months ago

akoshunyadi commented 4 months ago

What type of PR is this?

What this PR does / why we need it:

Prepare the release 1.1

Which issue(s) this PR fixes:

Special notes for reviewers:

Changelog input

Additional documentation

hdamker commented 4 months ago

@akoshunyadi Could you please change the release number to r1.1? See "API release numbers start at r1.1" within https://github.com/camaraproject/ReleaseManagement/blob/main/documentation/API_Release_Guidelines.md

I know that the sub project have done a release r0.6 previously, but now it is time to start into the numbering of the Fall24 release cycle ;-) r1.2 could also be an option, to show that it is already the second release within the current cycle.

hdamker commented 4 months ago

@akoshunyadi consider to add @camaraproject/release-management_maintainers as reviewers if the PR is there.

akoshunyadi commented 4 months ago

@akoshunyadi consider to add @camaraproject/release-management_maintainers as reviewers if the PR is there.

yes, I would wait until all PRs are merged, and the change-log is final

eric-murray commented 4 months ago

Github is not letting me make suggestions for the "Scope" section in the README, but I'd suggest putting the different functions in different bullet points. e.g.:

hdamker commented 4 months ago

Github is not letting me make suggestions for the "Scope" section in the README, but I'd suggest putting the different functions in different bullet points

The reason is that these lines are not changed by the PR. As this is also not within the scope of this PR, how about propose it in an issue and address it when some more Codeowners are again available? (it can perfectly done between RC and public release)