Motivation:
Complex features are commonly first developed in out-of-tree developments and then slowly merged step-by-step over multiple kernel releases (multiple merge windows). PaStA can be used to indicate how such a patch set evolves due to improvements or adjustments to upstream development and how the patch set is included over time.
Task:
For a given repository of a patch set, provide a generally applicable report with core metrics of the evolution over time.
The report should state:
how many out-of-tree patches are modified from one kernel release to the next,
how many out-of-tree patches were merged from one kernel release to the next,
which out-of-tree patches were provided for submission on the mailing list, which were discussed and with which intensity
Note: Ralf has already done this kind of evaluations for some examples. Possibly, we just need to provide documentation how this can be done with PaStA and show this with some few example evaluations.
Examples: PREEMPT_RT, gr_security, Xenomai, vendor-specific trees
Motivation: Complex features are commonly first developed in out-of-tree developments and then slowly merged step-by-step over multiple kernel releases (multiple merge windows). PaStA can be used to indicate how such a patch set evolves due to improvements or adjustments to upstream development and how the patch set is included over time.
Task: For a given repository of a patch set, provide a generally applicable report with core metrics of the evolution over time.
The report should state:
Note: Ralf has already done this kind of evaluations for some examples. Possibly, we just need to provide documentation how this can be done with PaStA and show this with some few example evaluations.
Examples: PREEMPT_RT, gr_security, Xenomai, vendor-specific trees