Versions Compared

Old Version 18

changes.mady.by.user Trevor Conn

Saved on

compared with

New Version 19

changes.mady.by.user Jim White

Saved on

Key

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

...

  • Revisiting holding and when work needs to enter holding (and what it takes to get out)
  • Acceptance of DS and testing needs - how to bring a new device service from holding to the EdgeX repos (presented by DS WG – Iain, Tony)
  • Bound checking issue (presented by Tony)
  • Apache 2 licensing requirements (per Tony E message and Brett P (LF) and Ducan (IOTech) responses.Whether it was necessary and wise to move code from EdgeX org to holding only to go back to EdgeX org again (vs just make a new repo directly in EdgeX) - initially covered in Jan 15, 2020 TSC
  • Address policy on patch/minor release based on discoveryof CVE or other security issue (high/critical) - would we force dot release of all services, just affected ones, ???  For Consul and Mongo, we just minor rev'ed those services and containers.  What if issue was in one of the go services?  Would we have to minor release all (example go from 1.2.0 to 1.2.1) on all services even if only one was affected?