Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Current »

Attendees & Representation

Type @ and your name to indicate your attendance

LF Staff: N/A

Community: Herbert Damker Samuel Adeyemo Jan Friman Ali Tizghadam Gabriel Iklaga Rafał A. (Unlicensed) @ Sachin Tanja de Groot 

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
    •  Review of milestones
  • Any Other Topics

Minutes

Action Item Review

DescriptionDue dateAssigneeTask appears on
  • RM team needs to add another CODEOWNER - Candidates welcome
2024-05-28 Release WG Minutes

Question on release requirement

Question on the reference to point 6 in the Check list here: the table is here Checklist.md in Commonalities

Is this still applicable ? yes, but the new definitions of the release types should clarify what 

Review of Milestones

Comments on table:

  • need to clarify the table in what is input to the miletone: change wording to past tense.
  • add more time for the commonalities milestone - discuss time in the TSC
  • move items from milestone 1 to milestone 2
  • move retro items after the release milestone
  • total is 17 weeks - some weeks can be added
  • two columns for commonalities (pre-release usable by sub-projects and M2) and one for sub-projects
  • put tasks between milestones
  • put DOD in the milestone line

Timeline discussion in the xxx conference - Herbert to complete please

MWC is about implementation, not CAMARA releases. Example: for MWC feb 24 implementation should use a meta-release from Sept 24.


Maturity of sub-projects

Proposal to look at introducing stages/categories (as in CNCF):

  • sandbox projects - easy to create
  • incubated projects - hard to get into 
  • mature projects - stable

2 Provider Implementations between sandbox and incubator.

If a project wants to get incubated they must at least be part of one meta release

Question: clarify how does this map to alpha/beta/release ? It will needs a picture.

Action items

  •  
  • No labels