08-24-2022 TSC Meeting Minutes
TSC Meeting Zoom link
Meeting Recording
Meeting Chat File
Attendees & Representation. Please add your name to the attendance table below.
Attendees | |
Name | Company |
@Daniel Havey | Microsoft |
@Eric Tice | Wipro |
@Jason Niesz | Walmart |
@Dave Thaler | Microsoft |
@Santhosh Fernandes | Walmart |
@Rohith R | Walmart |
@Jay Sheth | Walmart |
@Charles Lucas | Walmart |
@chaitanya lala | Microsoft |
@Charles Liu | Walmart |
LF Staff: @LJ Illuzzi @David McBride, @Kenny Paul
Agenda
Meeting note taker
Welcome to new attendees
Release Management Consultation
General Topics (cover as needed)
Use Cases
Roadmap
Project structure
Governance
Technical Steering Committee
Review PRs
Minutes/Updates
Release Management Consultation -
2 hours in total are needed to complete the consultation/Training
Hour 1: 08/23
Hour 2: ?
Next Week or a one off(?), closer together is better
Yes, scheduled.
Community Release Manager
1-2 people from community
RM for LFN Projects - David McBride
Dedicated RM does not scale - No RM is chaos - Find a middle ground
Need - a stable, effective, repeatable process.
Projects of projects - dependencies
chat: looks like the current L3AF "release process" (such as it is) is documented at https://github.com/l3af-project/governance/blob/main/docs/RELEASE_PROCESS.md. I'm guessing there are gaps we will hear about in this presentation.
L3AF is a project of projects: L3aF-arch, l3afd, epf program repo
Interop
1 proj w/mult releases: for eg: Linux/Windows.
MUST adhere to release schedule
L3AF project: New, release every 10-12 weeks
Currently no releases
More mature - longer release periods
Linux kernel - 4 times a year
Signoff process
TSC is not necessarily responsible for regular release signoff
The task may be delegated to another body
Use the principle of minimum viable governance
What about the PR around release?