Thanks Don,    I will be following up with the team later today and will have a plan for TFC-31.

-g

On 3/16/2021 9:53 AM, Don Harbin via Tf-openci-triage wrote:

Attendees: Karl, Don, Anton

Minutes:

- Quick meeting due to Don's last minute time change - sorry about that.
- ACTION:  Don - determine good meeting time.  Things really bad on the
Linaro side in that 2 hour window.  Seems bad on Arm side as well.
   - Propose moving back to 5:30am Don's time, but Don may only attend
   optionally.
- Matteo notes shared with Don prior to meeting:
   - I see some in-progresses which I assume are new (urgent?) stuff
   like 39, 49 and 50.
   - TFC-5 has been picked...that's ok but the most important prio thing
   is TFC-31 to deploy TF-A CI so if TFC-5 is small and quick,

OK..if it turns into huge work, I say park it and progress TFC-31 instead which is on the critical path...we need to deploy live TF_A even with tests disabled (becasue of TF-5) - TFC-25 is also not closed yet...but looking at Glen' last comment, there seems to be some minor things still open...I'd use the same rationale..if small fixes OK...else park them (and we can re-check with Joanna team afterwards) - We should really plan to deploy TF-A before the next Board meeting, as per Julius and general request (That means closing TFC-31 in the next 2-3 weeks...considering easter break!)

- Karl: OpenCI running more stable - ran 800 jobs and all passed.
- Don: Which tickets are critical to TF-M?
   - Karl: TFC-50 is a really strong candidate to reduce risk.
   - Don: A nice risk mitigator, but can be put below TFC-31?
   - Karl/Anton: Agreed
   - Anton: Agreed that nothing critical for TF-M so can move the TF-A
   tasks as needed.
- ACTION: Don to investigate with Glen how to get TFC-31 scoped and into
the In Progress as top priority to support our commit of having TF-A
deployed before April 14th.

Don