Release Process Development Meeting

You may subscribe to the meeting and get meeting logistics here.

June 4, 2021

Attendees: David McBride, Scot Steele , Jim Baker 

Agenda:

• Discuss email to team describing M1 tasks.  Who are the workstream leads?
• Review presentation material for release process session at Dev & Test Forum next week
• Update GitHub with release name string and milestone dates

Notes:

• M1 task email
  • Addressed by Pankaj response to my email
• Dev & Test Forum presentation review
  • Added slide regarding post sign off 
• GitHub updates
  • Pankaj unavailable, so deferring to next week

May 21, 2021 (CANCELED)

Canceled

May 21, 2021

Attendees: David McBride, Scot Steele , Pankaj.Goyal , Jim Baker , Al Morton

Agenda:

• Determine processes for milestone processes for M4 and M5
• Discuss self release process
• Schedule proposal for Lakelse

Notes:

• Text

May 14, 2021

Attendees: David McBride, Scot Steele , Pankaj.Goyal , Jim Baker , Al Morton

Agenda:

• Determine processes for milestone processes for M4 and M5
• Discuss self release process
• Schedule proposal for Lakelse

Notes:

• Text

May 7, 2021

Attendees: David McBride, Scot Steele, Pankaj.Goyal Al Morton

Agenda:

• Determine processes for milestone processes for M3 and M4
• Discuss Independent release process
• Schedule proposal for Lakelse

Notes:

• Release process principles
  • A project or workstream may slip an internal release milestone with TSC approval
  • A project or workstream may be included in the major release after the scheduled release, with TSC approval
    • The project must declare for the Supplemental  Release (M7, typically 2 to 4 weeks late) prior to the  M3 date.

Apr 30, 2021

Attendees: David McBride, Pankaj.Goyal, Emma Foley, Jim Baker, Scot Steele

Agenda:

• Determine processes for milestone criteria for M2 and M3
• Discuss Independent release process

Notes:

• Al Morton Test projects are fulfilling a list of test cases from the requirements listed in the Reference Conformance documentation 
  • Tests that are in the Reference Conformance verify the Reference Architecture/Reference Model
  • End user buy-in – validation of the RC/Anuket Assured badges have value in the acquisition process
  • Traceability: Every test in RC needs to be linked to a specification in RM/RA AND every spec item needs a test

Apr 23, 2021

Attendees: David McBride, Jim Baker, Pankaj.Goyal

Agenda:

• Review Release Process Milestone Planning and resolve issues
• Determine processes for milestone criteria

Notes:

• Small turnout this week due to OpenStack event.
• Completed documentation of processes for M1 and started on M2.
• Pankaj.Goyal shared template from Elbrus release used by work streams to document high level scope
• Gergely Csatari shared process for resolving feedback to specifications using GitHub Issues

Apr 16, 2021 (CANCELED)

Apr 9, 2021

Attendees: David McBride, Ildiko , Pankaj.Goyal Gergely Csatari, Al Morton, James Gu

Agenda

• Review Release Process Milestone Planning and resolve issues
• Determine processes for milestone criteria

Notes

• Text

Apr 2, 2021 (CANCELED)

Agenda

• Review Release Process Milestone Planning and resolve issues

Notes

• Text

Mar 26, 2021

Attendees: David McBride, Al Morton, Karine Sevilla, Olivier Smith, Karine Sevilla

Agenda

• Review Release Process Milestone Planning and resolve issues

Notes

• Reviewed comments in red from Pankaj.Goyal
• Clarified that the milestone table only indicates criteria for meeting the milestone (i.e., tasks finished), not how the activities are accomplished, or when they start. Those will be determined separately.
• Karine Sevilla suggested adding a task to finalize spec version numbering for M5.
• Al Morton suggested changing the M1 milestone name from "Release Planning" to "Release Definition".
• After above changes, milestone plan is at V .19.