Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 6079 invoked from network); 3 Mar 2009 16:43:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Mar 2009 16:43:16 -0000 Received: (qmail 94238 invoked by uid 500); 3 Mar 2009 16:43:14 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 94208 invoked by uid 500); 3 Mar 2009 16:43:14 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 94197 invoked by uid 99); 3 Mar 2009 16:43:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Mar 2009 08:43:14 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of zachary.zolton@gmail.com designates 74.125.46.28 as permitted sender) Received: from [74.125.46.28] (HELO yw-out-2324.google.com) (74.125.46.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Mar 2009 16:43:07 +0000 Received: by yw-out-2324.google.com with SMTP id 2so1512863ywt.5 for ; Tue, 03 Mar 2009 08:42:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=JerqWWVB1lm+kyGo/WGoZHeoinJ9et8z9k8Ic53bhv4=; b=xY1OEnRhY8K0wo/gAR3OiVDPOQ2xzi5Ppv5783ePz/5+efJB5TJP3Pe9E2+BBGtup3 1VxkPBJNTCp76tPB27XfvuiFC0jnCIVjEPJ6768iipF2UnxcBmYyJ6deHxh5O1jfXXgo jQRp21zO668JPRmrYvv8Ee4aXPoqsav/gsMYg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=QkzXIbJrWvvRZV0YULFUtTxrgrqNdeYqZ1Eo8jPbVDxRy2Np0ySysMrWGVY/oVk0pn Jl/GAFd+DBu5ta3QyQBZYXDAq/o4xm1yYqm/3GCJ1x8b/Ii0Y4oE+PuQHDPyYWm8V3Hy paTEOdVRZdwDHpZgzwAFTqIerEAKpSh7H1hD0= MIME-Version: 1.0 Received: by 10.100.216.10 with SMTP id o10mr5876251ang.86.1236098565864; Tue, 03 Mar 2009 08:42:45 -0800 (PST) In-Reply-To: References: <588B4EE0-77DD-48E8-AF35-973A623C2BAD@apache.org> <3b3520550903030401y346a8638k8b0c4d56bbb510e5@mail.gmail.com> <2BAB791A-875F-4681-8D3F-C10010BF4A87@apache.org> <074D9744-75EF-4E80-8868-6B54043E6F1D@apache.org> <20090303153520.GE4834@tumbolia.org> Date: Tue, 3 Mar 2009 10:42:45 -0600 Message-ID: Subject: Re: 0.9 release From: Zachary Zolton To: dev@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Okay, I get it. I can expect to have to re-import my data when upgrading to 0.10 release. Not a big deal, but a change in the API doesn't necessarily mean binary-compatibility-breaking changes to the data files. And, I don't think I've heard that mentioned, in particular. So, don't be snide, you rascals...! (^_-) On Tue, Mar 3, 2009 at 9:39 AM, Jan Lehnardt wrote: > - Show quoted text - > On 3 Mar 2009, at 16:35, Noah Slater wrote: > >> On Tue, Mar 03, 2009 at 04:30:56PM +0100, Jan Lehnardt wrote: >>> >>> On 3 Mar 2009, at 16:26, Zachary Zolton wrote: >>> >>>> Is there any notion of beyond which release we'd like to maintain >>>> binary data compatibility with the 1.0 release? >>> >>> The latest discussions revolved around having 0.10.0 the last pre-1.0 >>> release that introduces a new API and database file compatibility. >> >> Well, I don't think it matters, so what if we do a 0.11 or 0.12? >> >> All we are saying is that until 1.0, things may change. > > true. >