On 8 Jun 2016, at 7:13, Paul Jakma wrote:
On Wed, 8 Jun 2016, Martin Winter wrote:
So even in a set of 4 patches, I would test patch 1, patch 1+2, patch
1+2+3 and finally patch 1+2+3+4 ?
Or test each on it’s own?
The former would be enough I think. The latter would discourage
breaking up patches into easier to review 'stories'.
If you want me to try this, then suggest something (i.e. name of
accumulating branch?) and I can give it a try.
'proposed'?
Do you suggest the current proposed or a special proposed branch for the
CI system?
If we decide with the “proposed” tree workflow, then I’m not sure
if this should be a different branch
and let some maintainer cherry-pick commits into the current proposed.
Having a dedicated branch for this would also be preferred for me as
less risky in case my
scripts screw up :-) (at least for a trial phase)
- Martin
regards,
--
Paul Jakma | [email protected] | @pjakma | Key ID: 0xD86BF79464A2FF6A
Fortune:
It's amazing how much better you feel once you've given up hope.
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev