Re: Patch contribution tips
toggle quoted messageShow quoted text
Regarding the question about a way to run full non regression test, as mentioned by Jennifer, advice is to
use dedicated tool called twister:
About the warnings reported by compliance checks, we can indeed argue these are of minor importance
and could be derogated (especially in this case where effort was made to clearly document the change).
One reason not to derogate and do the requested change is that maintainers and release engineers (the
ones who merge) bandwidth is limited, so we're heavily relying on automated checks and verdicts.
This allows using github filters to get a list of PRs that are fulfilling all merge criterias. For instance,
here is the filter reporting PRs ready for merge:
(At the time I'm writing these lines, 17 PRs waiting for merge > list is long).
So even if derogating rules with automated checks would make sense in some cases, this actually requires
time to deviate from the process (ping people, agree that in that particular case deviation is justified, ....).
And of course, the more derogations are done, the more derogations are requested.
So getting compliance checks happy saves time (and then that time could be better spent in other tasks).
Hope it helps.
On Tue, 23 Mar 2021 at 21:21, Jennifer M Williams <jennifer.m.williams@...> wrote: