Il 19/02/2014 22:41, Chris Evich ha scritto:
On 02/19/2014 07:02 AM, Paolo Bonzini wrote:
Il 19/02/2014 09:17, Lukáš Doktor ha scritto:
Well no script can guarantee that.
No, but it can lay the grounds for continuous integration.
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).
In particular it makes automated bisection much much harder.
Stability is the goal of the tagged releases, and it doesn't make a lot
of sense to run big CI test jobs on the (often broken in some way) HEAD
master. As long as we stick to rapid, regular tagged releases, this
should be mostly "ok" for test development*
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.
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.
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.
Paolo
*Currently there are some TP repo-split "challenges" remaining, but this
was mostly an expected interruption and may last longer than we'd like.
Outside of this, lmr's been pretty good at getting releases out every
week or few.
_______________________________________________
Virt-test-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/virt-test-devel
