Thanks Alberto, while this is n't perfect yet (many would still need help to run the test as it isn't detailed enough yet for e.g. me desktop-noob) but you outlined what it is about - thanks.
But especially for a package like this which could be lost between kernel (owning it) and Desktop (everybody thinks it is theirs) - please let me ask a final question.
You are committing to do such tests:
a) after every upload
b) at least X times per cycle (manual CI)
c) combination of the above
And in that scope You = ?? Read - who commits to do that testing.
Per the MIR team meeting of today, once that is settled we think we can move forward on this case.
Thanks Alberto, while this is n't perfect yet (many would still need help to run the test as it isn't detailed enough yet for e.g. me desktop-noob) but you outlined what it is about - thanks.
But especially for a package like this which could be lost between kernel (owning it) and Desktop (everybody thinks it is theirs) - please let me ask a final question.
You are committing to do such tests:
a) after every upload
b) at least X times per cycle (manual CI)
c) combination of the above
And in that scope You = ?? Read - who commits to do that testing.
Per the MIR team meeting of today, once that is settled we think we can move forward on this case.