Re: ZK compatability
we should also point out that our ops guys here at yahoo! don't like the break at major clause. i imagine when we do the next major release we will try to be one release backwards compatible. (although we shouldn't promise it until we successfully do it once :) ben On 09/30/2010 10:29 AM, Patrick Hunt wrote: Historically major releases can have non-bw compatible changes. However if you look back through the release history you'll see that the last time that happened was oct 2008, when we moved the project from sourceforge to apache. Patrick On Tue, Sep 28, 2010 at 11:37 AM, Jun Raojun...@gmail.com wrote: What about major releases going forward? Thanks, Jun On Mon, Sep 27, 2010 at 10:32 PM, Patrick Huntph...@apache.org wrote: In general yes, minor and bug fix releases are fully backward compatible. Patrick On Sun, Sep 26, 2010 at 9:11 PM, Jun Raojun...@gmail.com wrote: Hi, Does ZK support (and plan to support in the future) backward compatibility (so that a new client can talk to an old server and vice versa)? Thanks Jun
Re: ZK compatability
Historically major releases can have non-bw compatible changes. However if you look back through the release history you'll see that the last time that happened was oct 2008, when we moved the project from sourceforge to apache. Patrick On Tue, Sep 28, 2010 at 11:37 AM, Jun Rao jun...@gmail.com wrote: What about major releases going forward? Thanks, Jun On Mon, Sep 27, 2010 at 10:32 PM, Patrick Hunt ph...@apache.org wrote: In general yes, minor and bug fix releases are fully backward compatible. Patrick On Sun, Sep 26, 2010 at 9:11 PM, Jun Rao jun...@gmail.com wrote: Hi, Does ZK support (and plan to support in the future) backward compatibility (so that a new client can talk to an old server and vice versa)? Thanks Jun
Re: ZK compatability
Looking forward, I don't think that anybody has even proposed anything that would require a major release yet. That should mean that you have quite a bit of lifetime ahead on the 3.x family. Moreover, it is a cinch to bet that even when a 4.0 is released, it is unlikely to have enough killer features to drive wholesale adoption right away. That means that there will be a 3.x bug-fix branch for quite a while even after 4.x versions come out. ZK has the least operations overhead of any software I have ever deployed in to a system. The worst problem is that you have to document procedures because you don't have to touch ZK often enough to remember them accurately. On Thu, Sep 30, 2010 at 10:29 AM, Patrick Hunt ph...@apache.org wrote: Historically major releases can have non-bw compatible changes. However if you look back through the release history you'll see that the last time that happened was oct 2008, when we moved the project from sourceforge to apache. Patrick On Tue, Sep 28, 2010 at 11:37 AM, Jun Rao jun...@gmail.com wrote: What about major releases going forward? Thanks,
