The "TDValidationReport.txt" was introduced although I'm not currently aware of its maturity or intended use. Guidance is sought on the appropriate way to handle application of TDs.
Note the current use case is that the editor manually applies all TDs as needed when an updated pass of a PP or module is done (e.g. if tasked to update to version 1.1, all TDs from 1.0 are reviewed and either applied or determined to be OBE) so it's not clear if a different process needs to be followed in the future (e.g. separate commits to apply separate TDs so that the deltas can be shown programmatically).
The "TDValidationReport.txt" was introduced although I'm not currently aware of its maturity or intended use. Guidance is sought on the appropriate way to handle application of TDs.
Note the current use case is that the editor manually applies all TDs as needed when an updated pass of a PP or module is done (e.g. if tasked to update to version 1.1, all TDs from 1.0 are reviewed and either applied or determined to be OBE) so it's not clear if a different process needs to be followed in the future (e.g. separate commits to apply separate TDs so that the deltas can be shown programmatically).