Re: [ClusterLabs] Pacemaker 2.0.1-rc4 now available
Ken Gaillot writes: > On Mon, 2019-02-25 at 12:48 +0100, wf...@niif.hu wrote: > >> Ken Gaillot writes: >> >>> We should be getting close to final release. >> >> How close are we to the final release? I'm asking because the Debian >> full freeze date is 2019-03-12 and migration requires 10 days now, >> thus I'd have to upload any significant changes ASAP to catch Debian >> buster. > > I got more distracted from the release schedule than I'd like, but I > think we're in good shape now. I'll put out a final release candidate > today to allow people at least a few days to test it -- would next > Monday or Tuesday be good enough for the final? FWIW, there shouldn't > be any significant changes from today's rc. It's tight, but possible. On the other hand, if the final is practically identical to rc5, this may be a non-issue. -- Thanks, Feri ___ Users mailing list: Users@clusterlabs.org https://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [ClusterLabs] Pacemaker 2.0.1-rc4 now available
On Mon, 2019-02-25 at 12:48 +0100, wf...@niif.hu wrote: > Ken Gaillot writes: > > > We should be getting close to final release. > > Hi Ken, > > How close are we to the final release? I'm asking because the Debian > full freeze date is 2019-03-12 and migration requires 10 days now, > thus > I'd have to upload any significant changes ASAP to catch Debian > buster. I got more distracted from the release schedule than I'd like, but I think we're in good shape now. I'll put out a final release candidate today to allow people at least a few days to test it -- would next Monday or Tuesday be good enough for the final? FWIW, there shouldn't be any significant changes from today's rc. -- Ken Gaillot ___ Users mailing list: Users@clusterlabs.org https://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [ClusterLabs] Pacemaker 2.0.1-rc4 now available
Ken Gaillot writes: > We should be getting close to final release. Hi Ken, How close are we to the final release? I'm asking because the Debian full freeze date is 2019-03-12 and migration requires 10 days now, thus I'd have to upload any significant changes ASAP to catch Debian buster. -- Thanks, Feri ___ Users mailing list: Users@clusterlabs.org https://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [ClusterLabs] Pacemaker 2.0.1-rc4 now available
On 30/01/19 11:07 -0600, Ken Gaillot wrote: > For those on the bleeding edge, the newest versions of GCC and glib > cause some issues. GCC 9 does stricter checking of print formats that > required a few log message fixes in this release (i.e. using GCC 9 with > the -Werror option will fail with any earlier release). A change in > glib 2.59.0's hash table implementation broke some of Pacemaker's > regression tests; for this release, these tests can be disabled with > the --disable-hash-affected-tests=try configure option Sorry, I am the culprit of that statement (fixed in the GitHub PR discussion since), but little I knew that autoconf will only honour extra value in the positive case, i.e., use --enable-hash-affected-tests=try ^^ instead if you want to rely on automatic disabling of affected tests per the configure-time detected glib version (or plain "--disable-hash-affected-tests" to disable them unconditionally; default is to have all of them enabled as usual). > (we'll make the tests compatible as soon as practical, and that > option will go away). -- Nazdar, Jan (Poki) pgpW9mDQho57b.pgp Description: PGP signature ___ Users mailing list: Users@clusterlabs.org https://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[ClusterLabs] Pacemaker 2.0.1-rc4 now available
Source code for the fourth release candidate for Pacemaker version 2.0.1 is now available at: https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.0.1-rc4 This candidate has a few more bug fixes. We should be getting close to final release. For those on the bleeding edge, the newest versions of GCC and glib cause some issues. GCC 9 does stricter checking of print formats that required a few log message fixes in this release (i.e. using GCC 9 with the -Werror option will fail with any earlier release). A change in glib 2.59.0's hash table implementation broke some of Pacemaker's regression tests; for this release, these tests can be disabled with the --disable-hash-affected-tests=try configure option (we'll make the tests compatible as soon as practical, and that option will go away). Everyone is encouraged to download, compile and test the new release. We do many regression tests and simulations, but we can't cover all possible use cases, so your feedback is important and appreciated. I will also release 1.1.20-rc2 with selected backports from this release soon. -- Ken Gaillot ___ Users mailing list: Users@clusterlabs.org https://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
