Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Attendees

Name

Company
Daniel HaveyMicrosoft
Eric TiceWipro
Jason NieszWalmart
Dave ThalerMicrosoft
Walmart
Rohith RWalmart
Jay ShethWalmart
Charles LucasWalmart
chaitanya lalaMicrosoft
Charles Liu Walmart














LF Staff: LJ Illuzzi David McBrideKenny Paul

...

  • 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?

Action Items

Future Agenda Items