2024-06-04 Release WG Minutes
Community Attendees:
@Herbert Damker @Rafal Artych @Tanja de Groot
Community Attendees:
LF Staff:
@Casey Cain
Agenda
Antitrust Policy
Agenda review
Action Items Review: see Release Management Working Group
Open Issue Review
Question on readiness checklist
Info object content
Minutes
Open Issue Review
Remove non-relevant folders from repo structure wg management
#32 opened last week by tanjadegroot
ok. action: Tanja to create PR.
Add API Release Guidelines (process extract) to RM project documentation
#30 opened 3 weeks ago by tanjadegroot
Action: Tanja to add comment from Herbert and leave 3 more days for review. Then merge and close.
Add new API readiness checklist documentation
#28 opened 3 weeks ago by tanjadegroot
Tanja to put better explanation on basic and enhanced tests, referencing the test guidelines.
Create a CHANGELOG_TEMPLATE.md within ReleaseManagement/documentation & update it according to API Release Process documentation
#25 opened 3 weeks ago by hdamker
ongoing by Tanja
Is there a need for association of API definition (yaml) to Commonalities, ICM or Meta Release version? enhancement
#27 opened last month by gmuratk
Agreement was that
API release numbers shall just be numbers (starting at r1.1) - no meta release info.
In the info object an extension for the release version of commonalities shall be included as follows:
x-camara-commonalities: 0.4.0
Action: @Rafal Artych to update the current PR on the Info object to include this camara-specific extension.
This extension is only in the OAS spec, it is not meant to be used at runtime (e.g. in headers).
No meta-release information will be included as this does not add anything.
No release of ICM will be included as it is implied by the version of Commonalities (can be found in Commonalities Changelog.md)
No meta-release tagging in GitHub shall be done as it does not add anything, and can have mistakes wrt to what is in the OAS file
Consolidation Issue for open points release management documentation release management
#9 opened on Oct 4, 2023 by shilpa-padgaonkar
Tanja to check what remains and propose solutions as needed.
Development and Release Branches documentation release management
#10 opened on Oct 3, 2023 by FabrizioMoggio
Tanja to request Fabricio if OK to close
Define mandatory end points URL in each project release management
#11 opened on Sep 13, 2023 by psidana1983
Moved to Govenance
Process to publish v1.0 of an API
#5 opened on Jul 25, 2023 by Kevsy
Tanja to request Kevin if OK to close
Define Release Management for CAMARA
#4 opened on Jul 21, 2023 by MarkusKuemmerle
Ongoing
API Versioning - Aggregation backlog question release management
#14 opened on Jul 6, 2023 by chrishowell
Backlog
Readiness Checklist step 6 update proposal release management
#16 opened on Jun 22, 2023 by FabrizioMoggio
Tanja to request Fabricio if OK to close
Question on readiness checklist
On the 2 checklist items - basic and enhanced testing - the question was raised:
Info object content
It was discussed that the proposed update to the Info Object includes fields with example values that MAY to be filled by the API provider.
A good point was made that such examples are not really needed for CAMARA, so they could be removed.
This concerns the Contact and
Action Rafal to update the pull request to add this change