Attendees & Representation

Type @ and your name to indicate your attendance

LF Staff: Casey Cain 

Community: Herbert Damker  @Gabriel Iklaga Sachin kumar Tanja de Groot Rafal Artych Mark Cornall 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 Managers
    • Release schedule & process - initial discussion
  • Any Other Topics

Minutes

Action Item Review

DescriptionDue dateAssigneeTask appears on
  • Tanja de Groot to send M0/M1 email after the next TSC meeting on thursday. After meeting note: this was updated in TSC meeting to send message on 06-24 when ICM rc is available 
Tanja de Groot2024-06-18 Release WG Minutes
2024-06-18 Release WG Minutes
Tanja de Groot2024-05-28 Release WG Minutes
  • RM team needs to add another CODEOWNER - Candidates welcome
2024-05-28 Release WG Minutes
  • Issue #5: check example on stable API version in RM pages and add if needed. Tanja de Groot 
Tanja de Groot2024-05-14 Release WG Minutes

Release Manager

  • Gabriel Iklaga will support Samuel from Nokia side
  • Request for further volunteers will be raised within the CAMARA Board meeting (on Thursday, Jan 25th)

Release Schedule - initial discussion

  • Work products needed:
    • Commonalities
    • Identity & Consent Management
    • Release Management
      • Overview of released APIs and their version and status
      • Release management process
    • For each (API) sub projects: 
      • API Definition(s)
        • Following the Commonalities guidelines
        • Successful linting check (with latest rules provided by Commonalities
        • Inline documentation, usable together with swagger editor and redoc
      • Test definitions
        • .feature files according to guideline from Commonality (comes with v0.2.0)
      • Supplementary documentation if needed to use or implement the API definition(s)
        • User documentation should be including the API Definition
  • Dependencies:
    • Release Management <= Commonalities, API Sub Projects
      • Needs information (e.g. scope definitions) about the planned and done releases from the sub projects
      • This information has to be provided in a way that can be automated collected
    • API sub project(s) <= Commonalities
      • all API Sub Projects need to know the release of the Commonalities documents and artefacts which they have follow for their release
    • Commonalities <= Identity & Consent management
      • Commonalities (a release of Commonalities is referring to documents within a release of I&CM)
  • Potential milestones:
    • Kick-off
      • and Scope of I&CM and Commonalities
      • 4 weeks
    • Release candidates of Commonalities
      • Scope defined per sub projects (could be part of one the previous lines)
      • 4 weeks
    • Release of Commonalities
      • 4-6
    • (First) Release Candidates of sub projects
      • 4-6 weeks
    • Sub project releases
      • 2 weeks
    • Common Release Date ("packaging done for the community release")
    • Release Retro
  • Release cadence:
    • 2 releases per year as a target
  • Initial schedule:

Guidelines towards Sub Projects regarding releases and versioning

Action items

  • Create first draft of release process document based on the input Samuel Adeyemo