Paul,
Imo we should leverage regression testing to identify which patches / patch
sets introduce problems and either skip those or get them fixed before
including them.
Set another way, for my prospective, pushing the portion of proposed 8 to
master that passes Martin's regression tests is reasonable; but pushing
code known to introduce problems isn't.
What about working with Martin to automatically go through the patch sets
and any that pass bring into his Auto branch. Then you or the patch
authors can work to resolve the problem introduced in the specific patch /
patch sets. What do you think?
Lou
On August 5, 2016 5:19:12 AM Paul Jakma <p...@jakma.org> wrote:
On Thu, 4 Aug 2016, Martin Winter wrote:
If someone has any other ideas, then please speak up.
If there are no conceptual objections to what's queued in ff, then we
continue with merging and fix the bugs later. No?
regards,
--
Paul Jakma | p...@jakma.org | @pjakma | Key ID: 0xD86BF79464A2FF6A
Fortune:
I know the answer! The answer lies within the heart of all mankind!
The answer is twelve? I think I'm in the wrong building.
-- Charles Schulz
_______________________________________________
Quagga-dev mailing list
Quagga-dev@lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagga-dev
