From dev-return-3267-apmail-couchdb-dev-archive=couchdb.apache.org@couchdb.apache.org Mon Mar 09 18:18:22 2009 Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 51126 invoked from network); 9 Mar 2009 18:18:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Mar 2009 18:18:22 -0000 Received: (qmail 64085 invoked by uid 500); 9 Mar 2009 18:18:20 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 64051 invoked by uid 500); 9 Mar 2009 18:18:20 -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 64040 invoked by uid 99); 9 Mar 2009 18:18:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Mar 2009 11:18:20 -0700 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 jchris@gmail.com designates 209.85.132.249 as permitted sender) Received: from [209.85.132.249] (HELO an-out-0708.google.com) (209.85.132.249) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Mar 2009 18:18:11 +0000 Received: by an-out-0708.google.com with SMTP id c37so764662anc.5 for ; Mon, 09 Mar 2009 11:17:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=IBs+pkSR67qz1wCssHjfQqChSxhzAN2vg56DoLAkqxo=; b=GERZ/f+85o5nj1S1fDQCIya3xiGASaxZ9XJ3AptAerCbPOWuivUMsWAutJ4Lv211Qz 0NMWTLBB3eXbYVE/n2tkN66L3XiomNyA7hH/0TmN+RBBGmoGGJprO5zG7tw6pWsm1jBR zfSpeHbU3PLy0YoCuJ693ifh+9c39DqhC5mqk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=IIDmX3dUpucbdnykhLN947X9OBWSQMRkJJqdV0PqdgCsPMekMB9Cco5KnzOM12Aaeq hn8t73HaVzv655m7FIaEH9zJMRh0c/bqpPZ/cbuNvdAGBLWJVlAWi5Pu6IbklzxGLN+e Zfjs6hX4BKUIvvuSMW5O1MF4ZctoRdzA5qDBo= MIME-Version: 1.0 Sender: jchris@gmail.com Received: by 10.142.214.11 with SMTP id m11mr2643607wfg.279.1236622669803; Mon, 09 Mar 2009 11:17:49 -0700 (PDT) In-Reply-To: <3BB778C2-C323-47E1-B17B-F5E7F0018F46@gmx.de> References: <33A2F492-1437-4FE5-BF42-0DD12A891F27@gmx.de> <3BB778C2-C323-47E1-B17B-F5E7F0018F46@gmx.de> Date: Mon, 9 Mar 2009 11:17:49 -0700 X-Google-Sender-Auth: 4d7433335d785104 Message-ID: Subject: Re: REST, Hypermedia, and CouchApps From: Chris Anderson 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 On Mon, Mar 9, 2009 at 11:14 AM, Christopher Lenz wrote: > Can you elaborate on what you mean with "soft landing"? Continuing to > support the old URLs for a while? How long? > heh. Sorta changed my mind on that in the last few days. My latest post to this thread is more accurate about what I think we should do: > My strategy for committing will be - commit to the branch I started > today. Notify the dev and user lists about the breaking change to view > urls. Merge the branch to trunk. I don't see much point in waiting > between the notification of the breaking change and the merge - people > who want time to convert their client libraries can hover at the > pre-merge revision until they are ready to leap to 0.9. > > Does this seem sane to you all? -- Chris Anderson http://jchris.mfdz.com