On Thu, May 6, 2010 at 9:29 AM, Florian Haas <[email protected]> wrote: > On 05/06/2010 08:59 AM, Andrew Beekhof wrote: >> About the only time I start heartbeat is for a few days before a release. >> And even then only for 1.0 releases, 1.1 is only tested against corosync. >> >>> Probably true, though the amount of testing LINBIT does on both >>> messaging layers is quite substantial. >> >> Any chance I could convince LINBIT to do the heartbeat testing as an >> "official" part of the process for 1.0 releases? >> That would certainly be a big help. > > We already run full CTS tests with the then-current Pacemaker 1.0 > release as part of the pre-release process for any new Glue or Heartbeat > release. Now if we could get Pacemaker RCs like I suggested right after > 1.0.8, I guess we could give those a CTS spin too. :)
You mean like this? http://www.clusterlabs.org/rpm-test/ This is how I get new builds onto my test boxes, so its always up-to-date. (There is also http://www.clusterlabs.org/rpm-test-next/fedora-12/src/ for 1.1 releases) I've also fiddled with the build script so that the version is always bumped (which will make yum happy). I still don't see the point of a formal RC process though, particularly for 1.0 which is deep into maintenance mode. I favor a "Start of release testing" + "End of release testing" approach with as few checkins as possible in-between. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
