Please add your comments / feedback on the RM process here:
Fall24
- add link to release PR review guidelines (M3) on Confluence in the review issue template (Guidance for release PR review - CAMARA Project - Confluence)
- https://github.com/camaraproject/ReleaseManagement/issues/83#issuecomment-2326205649 include the changelog titles guidelines e.g. "r1.1 - rc"
- API release tracker template updates
- remove "M5 date" field from the API release tracker template as for
...
- APIs M3 and M4 are the milestones
- reorder fields: M3 date; pre-release tag link; M4 date; pre-release tag link
- rename the "Target Maturity" to "Maturity"
- add a "RM status" field to hold links to GitHub RM review issues - can we show the issue status in confluence ?
- add an API definition field with a direct link to the yaml ?
- check guidelines on how to fill the "Repository" field should be just the repo name
- remove LICENSE file from TEST folder in repository template
- I think it would be an enhancement to reflect clearly per release since which version is the changelog consolidated, as kubernetes does for example:
- see: https://github.com/camaraproject/DeviceLocation/pull/252#issuecomment-2312647764 Edit th eCHANGELOG template to indicte this in the header of the major release section. - Kuberneters has a changelog folder with per release files per release - Tanja de Groot Tanja to chek
- Create an ICM review issue template for stable APIs or add these in the RM review issue template ? see ICM section in Guidance for release PR review
- update template text "Telco Operator as API provider" to "API provider"