We can also look for issues that are still open (and are delaying 3.4
to be marked as stable), and make the call whether we can use it or
On Thu, Jun 28, 2012 at 11:48 AM, Andrew Purtell <[EMAIL PROTECTED]> wrote:
> ZooKeeper dev consensus is: "fwiw during the summit meetup we took a
> poll and the consensus was
> that 3.4 should now be considered stable"
> So I don't see an issue with depending on 3.4.x. At some point you
> have to make progress.
> ---------- Forwarded message ----------
> From: Patrick Hunt <[EMAIL PROTECTED]>
> Date: Thu, Jun 28, 2012 at 9:18 AM
> Subject: Re: porting multi() to zookeeper 3.3
> To: [EMAIL PROTECTED]
> Cc: Jesse Yates <[EMAIL PROTECTED]>
> On Thu, Jun 28, 2012 at 6:54 AM, Ted Yu <[EMAIL PROTECTED]> wrote:
>> See Jesse's comment:
> Sounds like a reasonable concern. In their shoes I'd probably stick
> with established/stable features as well.
> fwiw during the summit meetup we took a poll and the consensus was
> that 3.4 should now be considered stable. Mahadev and I were planning
> to propose the next release (3.4.4) as such. So it shouldn't be long
> to wait if you are interested in using some of the new features.
>> On Thu, Jun 28, 2012 at 12:07 AM, Patrick Hunt <[EMAIL PROTECTED]> wrote:
>>> On Wed, Jun 27, 2012 at 10:11 PM, Ted Yu <[EMAIL PROTECTED]> wrote:
>>> > For Ted's question, developers and ops at the company I mentioned would
>>> > able to give their answer.
>>> We have a general policy of not adding new features to fix releases.
>>> What testing have you done with 3.4.3 that concerns you? Are there
>>> specific outstanding bugs?
> Best regards,
> - Andy
> Problems worthy of attack prove their worth by hitting back. - Piet
> Hein (via Tom White)