On Fri, Feb 1, 2013 at 2:47 PM, Kashif Jawed Siddiqui <kashi...@huawei.com> wrote: > Well, It should be Ok. > > Eagerly waiting for the Pacemaker 2.0 Release. (expecting atleast by March)
I think March might be pushing it. Guest management is a pretty big feature. I should probably do another 1.1 release soon-ish (next week or so) to get the latest round of bug fixes out there while we finish off 2.0 > > Regards, > Kashif Jawed Siddiqui > *************************************************************************************** > This e-mail and attachments contain confidential information from HUAWEI, > which is intended only for the person or entity whose address is listed > above. Any use of the information contained herein in any way (including, but > not limited to, total or partial disclosure, reproduction, or dissemination) > by persons other than the intended recipient's) is prohibited. If you receive > this e-mail in error, please notify the sender by phone or email immediately > and delete it! > > ________________________________________ > From: Andrew Beekhof [and...@beekhof.net] > Sent: Thursday, January 31, 2013 4:24 PM > To: The Pacemaker cluster resource manager > Subject: Re: [Pacemaker] Release Date for Pacemaker 1.2 > > On Wed, Jan 30, 2013 at 10:46 PM, Kashif Jawed Siddiqui > <kashi...@huawei.com> wrote: >> Hi, >> >> >> >> I would like to know the planned releases for Pacemaker 1.2 / 2.0. >> >> >> >> Can you help me know approximate date or any link to find exact >> information ? > > It was going to be earlier this month, but then people got motivated > to do management of services inside guests (which are also cluster > resources). > My current thinking is that we'll wait for that to be finished and call it 2.0 > > Does that help? > >> >> >> >> >> >> Regards, >> Kashif Jawed Siddiqui >> >> >> *************************************************************************************** >> This e-mail and attachments contain confidential information from HUAWEI, >> which is intended only for the person or entity whose address is listed >> above. Any use of the information contained herein in any way (including, >> but not limited to, total or partial disclosure, reproduction, or >> dissemination) by persons other than the intended recipient's) is >> prohibited. If you receive this e-mail in error, please notify the sender by >> phone or email immediately and delete it! >> >> >> _______________________________________________ >> 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
