2023-11-28 Release WG Minutes

Owned by Casey Cain
Last updated: Nov 29, 2023
2 min read

Attendees & Representation

Type @ and your name to indicate your attendance

LF Staff: @Casey Cain @David McBride 

Community: @Jan Friman @Ming Hui Foo @Ludovic Robert @joseantonio.ordonezlucena @Ali Tizghadam @Jose Luis Urien Pinedo

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

  • General Topics

    • Continuation of RM training provided by @David McBride  

  • Any Other Topics

Minutes



Recap

  • @David McBride provided a brief recap of the discussions from last week

    • David noted the importance of listing the work products expected to be released in a given release cycle.

    • Not every sub-project is expected to participate in every release cycle, hence the importance of identifying the participants at the beginning of the release cycle.

    • He also noted the importance of documenting the work process steps and dependencies.

    • It was also noted that the release process should be a living document that evolves over time

Identifying Milestones and Tasks

  • David said that they will cover milestones in part 3 of the training further, but noted that they will be a useful metric to ensure that the release process is on schedule.

  • David recommended that there should be no more than 5-6 milestones to reduce the overhead complexity of the release.

  • Recommended milestones are

    • Requirements definition

    • Feature complete

    • Component test

    • Integration test

    • Documentation

    • Packaging

  • @Jan Friman noted that it may be difficult to implement some of these milestones.

    • @David McBride confirmed that these are just suggested milestones. 

    • You may also find yourself in a situation where you're not ready to implement some tests, which means you may not be ready to participate in the "current" release cycle.

  • Remember that milestones should be common across projects as much as possible and verifiable.  

    • Sometimes a milestone looks good on paper; but is very difficult to verify in practice.  This should be avoided.

  • A wiki table is a good way to track and allocate milestones.

Preparing a schedule template

  • This may not show the exact dates, but rather the expected time to accomplish those tasks.

  • Don't worry about making it perfect the first time.  This will likely be an iterative process as we refine the tasks. 

  • We will also need to identify our cadence for the release.

    • It is common to have a 6 month cadence.  However we should be looking at our requirements for milestones, holidays, and major events that could impact the process. 

Socialize the Release Process and seek TSC approval

  • @David McBride spoke about socializing the documented release process to solicit community feedback before approaching the TSC for approval

Action items