2024-06-04 Release WG Minutes

Community Attendees:

@Herbert Damker @Rafal Artych ย @Tanja de Grootย 

Community Attendees:

LF Staff:

@Casey Cainย 

Agenda

Antitrust Policy

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

Action items

Tanja to check with Fabricia on #10 and #16
Tanja to check with Kevin on #5
Rafal to add the x-camara-commonalities: 0.4.0 to the Info Object and associatedย  guidelines.
Rafal to update the pull request to remove Info Object fields that should be provided by API providers and keep only generic parts.