Return-Path: Delivered-To: apmail-hadoop-zookeeper-user-archive@minotaur.apache.org Received: (qmail 92373 invoked from network); 1 Oct 2010 00:43:57 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 1 Oct 2010 00:43:57 -0000 Received: (qmail 20985 invoked by uid 500); 1 Oct 2010 00:43:56 -0000 Delivered-To: apmail-hadoop-zookeeper-user-archive@hadoop.apache.org Received: (qmail 20932 invoked by uid 500); 1 Oct 2010 00:43:56 -0000 Mailing-List: contact zookeeper-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: zookeeper-user@hadoop.apache.org Delivered-To: mailing list zookeeper-user@hadoop.apache.org Received: (qmail 20919 invoked by uid 99); 1 Oct 2010 00:43:56 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Oct 2010 00:43:56 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ted.dunning@gmail.com designates 209.85.216.176 as permitted sender) Received: from [209.85.216.176] (HELO mail-qy0-f176.google.com) (209.85.216.176) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Oct 2010 00:43:48 +0000 Received: by qyk36 with SMTP id 36so3293255qyk.14 for ; Thu, 30 Sep 2010 17:43:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type; bh=21w/qpFTOc+ObH46hPjDrqFsAMoCkOicTDKkN91wqgU=; b=KdL4r3106IwZYDtzWbpgwcWHnsYGcT7Nmx3T2U4AKtBiauuTX39m8MXZwI6t6hoqeu SvYzLVcqyoAjTfahHgitdRzq/qPzVnzgXL+VxJ8BEG70LGaWeik42ILZsONUjKPg/at6 9lpFFq/YSkuTaDmeaHiJI/AM+ZwBjdcl5FDnI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=uQ7QLiu3XUuaMeMo+FJs1ywP7UJUbJ0+TBKTCVpMrSB2a6dNVPIgWs7U5Y1jttbYvs +rrbEDgOXPvOpiBEvY2iFhzQb5K9MoeQHSfImrTXWkiaqBTLd4LH0/RqkeMgus1iDa/u CzpuSVfHIFyjV7tHAlVglMYsv0bqXoLGjzCVM= Received: by 10.220.200.194 with SMTP id ex2mr164328vcb.0.1285893806959; Thu, 30 Sep 2010 17:43:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.179.195 with HTTP; Thu, 30 Sep 2010 17:43:06 -0700 (PDT) In-Reply-To: References: From: Ted Dunning Date: Thu, 30 Sep 2010 17:43:06 -0700 Message-ID: Subject: Re: ZK compatability To: zookeeper-user@hadoop.apache.org Cc: junrao@gmail.com Content-Type: multipart/alternative; boundary=90e6ba53a0c0952d850491837b0e X-Virus-Checked: Checked by ClamAV on apache.org --90e6ba53a0c0952d850491837b0e Content-Type: text/plain; charset=UTF-8 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 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 wrote: > > > What about major releases going forward? Thanks, > --90e6ba53a0c0952d850491837b0e--