2024-03-12 Release WG Minutes

Owned by Casey Cain
Last updated: Jun 13, 2024 by Tanja de Groot
2 min read

Attendees & Representation

Type @ and your name to indicate your attendance

LF Staff: @Casey Cain 

Community: @Tanja de Groot @Gabriel Iklaga @Jan Friman @Sachin kumar @G. Murat Karabulut @Samuel Adeyemo 

Agenda

The project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.

  • Roll Call

  • Action Items Review

  • Agenda Bashing

  • General Topics

    • release milestone table improvements

    • alfa-beta releases

    • classification of project (incubation)

  • Any Other Topics

Minutes

Action Item Review

Topic 1: Release milestone table improvement

  • The updated table is here: Meta-release Milestones

  • Review will be done as follows:

    • present one slide to the all hands call on thursday

    • send an email to the ALL mailing list for the review asking for comments on the Confluence page using the comment feature

    • deadline for comments March 28th

    • presentation to TSC on 21st 

  • Comments:

    • add a title to the 3rd column 

    • look at other release processes: OpenDaylight, ONAP, etc.

Topic 2: alpha-beta releases

Strong recommendation from Casey NOT to use alfa/beta release  

API sub-projects should just use API versions

Proposals is to write a proposal based on

  • SemVer standard, and 

  • define the link to the GitHub tags on the released branch and

  • the name of the GitHub release.

 

Topic 3: classification of API sub-projects

  • pushed to next week - Needs a proposal to be discussed as input to the meeting

  • Rafal to discuss with Herbert to write a proposal in confluence - it is about which APIs are mature enough to be taken into the meta release. Alternatively, all API sub projects could provide some version - with minimum requirements to be defined. 

  • Tanja view: define sets of requirements to pass for alpha, beta and meta release. Up to the API project to decide if to push an API to the meta release.

 

Topic 4: next week agenda

  • release management process