Anuket Project

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

Compare with Current View Page History

« Previous Version 45 Next »

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

Sept 3, 2021 (Canceled)

Attendees: Pankaj GoyalScot SteeleEmma FoleySandra Jackson Cedric Ollivier Al Morton Rihab Banday

Agenda:

  • Discuss any remaining issues with M2 (Aug 31)
  • Discuss M3 - Oct 19

Notes:

  • Meeting canceled due to lack of attendees (likely because it's the day before a 3-day weekend)

August 27, 2021

Attendees: Pankaj GoyalScot SteeleEmma FoleySandra Jackson Cedric Ollivier Al Morton Rihab Banday

Agenda:

  • Review status of Lakelse release in advance of M2 on Aug 31.

Notes:

  • Text

August 20, 2021 (Canceled)

Canceled due to confusion over the bridge info.

Attendees: Pankaj GoyalScot SteeleEmma FoleySandra Jackson Cedric Ollivier Al Morton Rihab Banday

Agenda:

Notes:

  • Text

August 13, 2021

Attendees: Pankaj GoyalScot SteeleEmma FoleySandra Jackson Cedric Ollivier Al Morton Rihab Banday

Agenda:

Notes:

  • There are two bridges listed for the meeting, this causes confusion on joining - needs to be fixed
  • Focus on answering the question: Is this testable, as opposed to scoping a particular release

August 6, 2021

Attendees: David McBridePankaj GoyalScot SteeleSridhar RaoGeorg KunzRihab BandayEmma FoleySandra Jackson

Agenda:

Notes:

  • Group consensus that we focus on RA2, with RA1 left for offline review.
  • Pankaj suggests skipping 2.2 and beginning with section 2.3.
  • Emma suggests that we have a mapping between tests and requirements (i.e., which tests apply to a specific requirement)
    • Does this already exist?
  • We will initially review only "must", then later review "should" requirements if there is time.
  • Reviewed table 2.3 through requirement req.inf.ntw.10.
  • Scot and Emma to host next week's meeting (Aug 13)

July 30, 2021

Attendees: David McBridePankaj GoyalScot SteeleAl Morton

Agenda:

  • Review M2 Tasks

Notes:

  • Need to organize review of RA1 and RA2
    • Assign review to software project PTLs
    • Break out requirements into tables
    • Conduct standup review with PTLs in release meeting to check progress
    • Al suggests that we discuss in TSC meeting
    • New sections created:  https://wiki.anuket.io/x/3410

July 23, 2021 (Canceled)

July 16, 2021 (Canceled)

July 9, 2021

Attendees: David McBridePankaj GoyalScot SteeleCedric OllivierJim Baker

Agenda:

  • Review M1 Status
  • Meeting canceled next two weeks (July 16, July 23)

Notes:

  • RI lags dependency on RA (i.e., RI depends on previous release of RA)
  • RC is dependent on current development of RA
  • Cedric willing to be workstream lead for RC1/RC2 based on no changes to CI through the Lakelse release.
  • TSC needs to make a decision about RI criteria for release in terms of how much of RC the RI can pass
    • Discuss with TSC
    • One proposal:  set a minimum threshold percentage, then publish results with RI release
    • Need to be clear about threshold measurement
  • Cedric emphasizes that status/stability of RELENG will affect the success of the Lakelse release
  • Next meeting July 30

July 2, 2021 (Canceled)

June 25, 2021

Attendees: David McBridePankaj GoyalAl MortonScot Steele

Agenda:

  • Review M1 Status
  • Meeting canceled next week (July 2)

Notes:

  • Discussed status of M1
    • Still missing most project release plans
    • RC/RI planning page is mostly incomplete
    • Schedule for M1 appears to be at risk
  • Noted that there is some disagreement/confusion about traceability between specifications and software artifacts (e.g., RC/RI ==> RA)

June 18, 2021 (Canceled)

June 11, 2021

Attendees: David McBrideJim Baker , Pankaj Goyal

Agenda:

  • Review M1 Status
  • Update GitHub with release name string and milestone dates
  • Self release process
  • Meeting canceled next week (June 18)

Notes:

  • Reviewed status of CNTT/ GitHub
    • Milestones already entered
    • Pankaj added label for "Lakelse"

June 4, 2021

Attendees: David McBrideScot 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 McBrideScot Steele , Pankaj Goyal , Jim Baker , Al Morton

Agenda:

Notes:

  • Text

May 14, 2021

Attendees: David McBrideScot Steele , Pankaj Goyal , Jim Baker , Al Morton

Agenda:

Notes:

  • Text

May 7, 2021

Attendees: David McBrideScot SteelePankaj Goyal Al Morton

Agenda:

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 McBridePankaj GoyalEmma FoleyJim BakerScot 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 McBrideJim BakerPankaj 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 McBrideIldiko VancsaPankaj Goyal Gergely CsatariAl MortonJames Gu

Agenda

Notes

  • Text

Apr 2, 2021 (CANCELED)

Agenda

Notes

  • Text

Mar 26, 2021

Attendees: David McBrideAl MortonKarine SevillaOlivier SmithKarine Sevilla

Agenda

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.


  • No labels