On 02/19/2014 05:21 PM, Paolo Bonzini wrote: > Il 19/02/2014 22:41, Chris Evich ha scritto: >> To re-emphacize what Lukáš said, we've replaced 'next' with master and >> (mostly) weekly (or bi-weekly) tagged-versions. The concept of a >> 'stable' HEAD master is almost completely gone (though we try). > > Which isn't a good thing, especially since you don't have > stabilization/freeze periods (apart from exceptional cases like the TP > repository split).
I agree, and think stabilization/freeze periods are often overlooked/bypassed due to deadline time-constraints. These would help a lot, you're right. > The point of continuous integration is to have a good quality master > branch at all times, and an integration branch like linux-next helps a > lot for that. We found this not to be the case and maintaining next placed extra burden on lmr. In order for CI to be meaningful to core and test developers, we need to run large collection of tests that requires a lot more time/resources that we have available. Those that would benefit from knowing about some failure, would (on average) have to wait half of "a long time" for results. In our case, half is still "a long time". So it's more practical to just have master, and "do the best we can" about keeping it mostly stable (we're human). > If you cannot achieve good quality for the master branch, to me this is > a huge warning sign that you need more screening of what goes into > master, before it gets there. I agree here too, and this is the reason for $SUBJECT and the work lmr is doing on check_patch.py. Yes, it does place a lot of the burden onto the reviewers. > It's a vicious circle, and the negative feedback can be pretty violent > too. If master quality goes down too much, people will stop using it > for development, and the quality of tagged releases will go down. No disagreement from me here either, we need to keep a real careful eye on this, you're right. -- Chris Evich, RHCA, RHCE, RHCDS, RHCSS Quality Assurance Engineer e-mail: cevich + `@' + redhat.com o: 1-888-RED-HAT1 x44214 _______________________________________________ Virt-test-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/virt-test-devel
