Return-Path: X-Original-To: apmail-incubator-callback-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-callback-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 58E0AC2C7 for ; Tue, 10 Jul 2012 19:47:17 +0000 (UTC) Received: (qmail 68070 invoked by uid 500); 10 Jul 2012 19:47:17 -0000 Delivered-To: apmail-incubator-callback-dev-archive@incubator.apache.org Received: (qmail 68047 invoked by uid 500); 10 Jul 2012 19:47:17 -0000 Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: callback-dev@incubator.apache.org Delivered-To: mailing list callback-dev@incubator.apache.org Received: (qmail 68039 invoked by uid 99); 10 Jul 2012 19:47:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Jul 2012 19:47:17 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of pmuellr@gmail.com designates 209.85.160.175 as permitted sender) Received: from [209.85.160.175] (HELO mail-gh0-f175.google.com) (209.85.160.175) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Jul 2012 19:47:12 +0000 Received: by ghbz2 with SMTP id z2so402611ghb.6 for ; Tue, 10 Jul 2012 12:46:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=5xWBxmTNMyRWtn9FDu6gmJyIXajezu2REpLlYW9iiZY=; b=Z4PRtdPqYTJljQaj8pzbIwGEyu13ku1su/6N9neU5mQ+2523VDwljAbTkeYDhRPgp+ UMBXfeJo2FGg/yO9mzzc4znCHf3AqtCUAOfzxB5Nsj/NVhAAlHdk/NNXnYYGaEET6VKA EbYEz8Ek0zz+PMZcWqlzveM2+9C/zqZ4g6CEr5UIvoCM+S+QC5GrNY+A15eb6nKrG+JY rkj20oqLx2+XBgwdvj/X6X1nZElF1sXK0vihOGopJhMCrlVTf3DZoekBql03yeKZvztA ogzzBODL6I6Rhy732xpxXqK2KRcrsLJ1hx8auzd00PRRsTl7W6LoImii8D3TQZVUs/NB VXtg== MIME-Version: 1.0 Received: by 10.50.159.135 with SMTP id xc7mr12649872igb.1.1341949611654; Tue, 10 Jul 2012 12:46:51 -0700 (PDT) Received: by 10.231.45.146 with HTTP; Tue, 10 Jul 2012 12:46:51 -0700 (PDT) In-Reply-To: References: Date: Tue, 10 Jul 2012 15:46:51 -0400 Message-ID: Subject: Re: [iOS] Postponement of ARC support in 2.0 From: Patrick Mueller To: callback-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=14dae9399de1e8bd6804c47efd54 X-Virus-Checked: Checked by ClamAV on apache.org --14dae9399de1e8bd6804c47efd54 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Jul 10, 2012 at 3:17 PM, Brian LeRoux wrote: > Agree, this will be a whole lot easier to figure out in a F2F over > beers but obviously will bring everything back to the list to make any > final decisions. Of course. > One thing I'd like to add: cadence has nothing to do w/ deprecation > policy. Shipping on a regular heartbeat is a completely different > concern from the actual artifacts being shipped. > Here's an example / generalization of cadence that you might see with an even/odd release stream: fixes/enhancements to stable that don't break API - version change: x.(even).z -> x.(even).(z+1) eg, 2.0.0 -> 2.0.1 - occur as needed, hopefully/presumably not often monthly cadence for developers in dev stream - version change: x.(odd).z -> x.(odd).(z+1) eg, 2.1.3 -> 2.1.4 - every 4 weeks, or whatever major release - version change: x.(odd).z -> x.(odd+1).0 eg, 2.1.42 -> 2.2.0 - every so many months? Presumably the version numbers have matching branches/tags in git, as appropriate, for both even and odd releases. Would be interesting to see exactly how node does that (perusing their branches/tags right now ...) -- Patrick Mueller http://muellerware.org --14dae9399de1e8bd6804c47efd54--