From dev-return-18131-apmail-couchdb-dev-archive=couchdb.apache.org@couchdb.apache.org Fri Sep 16 01:09:02 2011 Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B019F83DE for ; Fri, 16 Sep 2011 01:09:02 +0000 (UTC) Received: (qmail 632 invoked by uid 500); 16 Sep 2011 01:09:02 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 570 invoked by uid 500); 16 Sep 2011 01:09:02 -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 562 invoked by uid 99); 16 Sep 2011 01:09:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Sep 2011 01:09:02 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of randall.leeds@gmail.com designates 209.85.210.180 as permitted sender) Received: from [209.85.210.180] (HELO mail-iy0-f180.google.com) (209.85.210.180) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Sep 2011 01:08:55 +0000 Received: by iahk25 with SMTP id k25so2712825iah.11 for ; Thu, 15 Sep 2011 18:08:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=o+SSq5sLJ3o7WrGQyfNMMKmaSd14pQQRZxAoHHXJwGE=; b=G2RotcLBl3p0gW0sHvCJy+DzQDQljxdZYd8OqRvSqzmwEQ/Br4DiugvZP7+DX90li7 AR5hN8TG9QKFvAVz3UHV8eH8v3agGvqmkx5Vx9kaqjOVBEfjjV0zg+b4nK7u4LVVd01c iOo+rYi5FK+5pO6QfSehYcNi1805idaLQRGr4= MIME-Version: 1.0 Received: by 10.42.146.202 with SMTP id k10mr345504icv.49.1316135315131; Thu, 15 Sep 2011 18:08:35 -0700 (PDT) Received: by 10.42.222.193 with HTTP; Thu, 15 Sep 2011 18:08:35 -0700 (PDT) In-Reply-To: <58807786-E059-4FA8-A5A2-3A8E6EB38D02@apache.org> References: <483B79DD-1D24-455C-A262-55C813D4EE53@apache.org> <58807786-E059-4FA8-A5A2-3A8E6EB38D02@apache.org> Date: Thu, 15 Sep 2011 18:08:35 -0700 Message-ID: Subject: Re: Branching 1.2.x From: Randall Leeds To: dev@couchdb.apache.org Content-Type: multipart/alternative; boundary=90e6ba6e8e9cef4d2b04ad04a11e --90e6ba6e8e9cef4d2b04ad04a11e Content-Type: text/plain; charset=UTF-8 On Mon, Sep 12, 2011 at 09:07, Noah Slater wrote: > > On 12 Sep 2011, at 16:35, Jan Lehnardt wrote: > > > The fact that we branch 1.2.x won't mean we can't get more tickets in > there, it's just to unblock trunk for post-1.2.x commits. I hope this makes > sense and I hope you all agree. > > How are we going to stop a repeat of the 1.0 release branch "kitchen sink" > problems? 1) Branch early 2) Stabilize 3) Bake 4) Make frequent point releases If we make the release branch earlier it can't possibly suffer kitchen sink and we can all thrash trunk a little harder. That's my vote, anyway. --90e6ba6e8e9cef4d2b04ad04a11e--