...
Attendees: David, Muddasar, Amy, Thomas, Tony, Kenny, Eric, Cedric
- Re-cap from Dec 13 - discussion
- Thomas says that we should start with dependencies at the project level, since we don't have an obvious way to get repo level dependencies
- Eric made an attempt to create a dependency graph.
- Very complex and time consuming manual operation! However, we believe that relationships are stable, so this may be worthwhile.
- Note that some dependencies are optional; however, the map does not currently differentiate between optional and required.
- Cedric suggests an alternative, automated way to identify dependencies: develop script to analyze code and detect REST calls
- Eric / Cedric to test with one or two components and report back to this meeting (next week?)
- What might process look like? (tentative)
- Release management task: PTLs review JSON file and make updates to dependencies
- This would be a pre-requisite to the architectural review between M1 and M2
- Run dependency tool to create map
- Review map against unmaintained projects list
- Who would do this?
- PTL / arch subcommittee
- Create Jira ticket to identify and track dependency?
- Who would do this?
- Start countdown clock for projects to remove dependency
- TSC must decide policy on how quickly dependencies must be resolved
- Strict: no release with dependencies
- Flexible: dependencies resolved over 2 or more releases
- TSC must decide policy on how quickly dependencies must be resolved
- Release management task: PTLs review JSON file and make updates to dependencies
Dec 13, 2021
Attendees: David, Pawel, Tony, Chaker, Thomas, Kenny
...