25.06.2013, 09:49, "Andrew Beekhof" <and...@beekhof.net>: > On 25/06/2013, at 2:33 PM, Andrey Groshev <gre...@yandex.ru> wrote: > >> 25.06.2013, 04:46, "Andrew Beekhof" <and...@beekhof.net>: >>> On 24/06/2013, at 3:44 PM, Vladislav Bogdanov <bub...@hoster-ok.com> wrote: >>>> 24.06.2013 04:17, Andrew Beekhof wrote: >>>>> Either people have given up on testing, or rc5[1] is looking good for >>>>> the final release. >>>> Is it going to be 1.1.10 or 1.2.0 (2.0.0)? >>> First its going to be 1.1.10 and, if there is still no-one screaming, >>> after a couple of weeks it will become 2.0[.0] >> What is really new in this version to change the major version? > > Compared to what? To 1.1.10 hopefully nothing, but that was always the point. > >> So far there are changes in the interface and API. >> IMHO, a stable product should not be such. > > 1.1 is not a stable branch, thats the entire point of re-releasing 1.1.10 as > 2.0: > > http://blog.clusterlabs.org/blog/2010/new-pacemaker-release-series/ > > Only instead of stopping development in 2010 and releasing 1.2.0, we kept > going and the subsequent 4511 changesets and "3490 files changed, 410422 > insertions(+), 144311 deletions(-)" justify the 2.0 moniker. >
Ok, I recently became engaged in the PСMK, so for me it is a surprize. The more so in all the major linux distributions version 1.1.х. >>>>> So just a reminder, we're particularly looking for feedback in the >>>>> following areas: >>>>> >>>>> | plugin-based clusters, ACLs, the new –ban and –clear commands, and >>>>> admin actions >>>>> | (such as moving and stopping resources, calls to stonith_admin) >>>>> which are hard >>>>> | to test in an automated manner. >>>>> | >>>>> | Also any light that can be shed on possible memory leaks would be >>>>> much appreciated. >>>>> >>>>> I would very much like to hear the observations (good or bad) of people >>>>> that have taken it for a spin. >>>>> >>>>> -- Andrew >>>>> >>>>> [1] >>>>> http://blog.clusterlabs.org/blog/2013/release-candidate-1-dot-1-10-rc5/ >>>>> _______________________________________________ >>>>> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >>>>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >>>>> >>>>> Project Home: http://www.clusterlabs.org >>>>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >>>>> Bugs: http://bugs.clusterlabs.org >>>> _______________________________________________ >>>> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >>>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >>>> >>>> Project Home: http://www.clusterlabs.org >>>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >>>> Bugs: http://bugs.clusterlabs.org >>> _______________________________________________ >>> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >>> >>> Project Home: http://www.clusterlabs.org >>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >>> Bugs: http://bugs.clusterlabs.org >> _______________________________________________ >> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >> >> Project Home: http://www.clusterlabs.org >> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >> Bugs: http://bugs.clusterlabs.org > > _______________________________________________ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org