Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 85555 invoked from network); 2 Jul 2009 18:50:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 2 Jul 2009 18:50:21 -0000 Received: (qmail 64177 invoked by uid 500); 2 Jul 2009 18:50:31 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 64125 invoked by uid 500); 2 Jul 2009 18:50:31 -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 64115 invoked by uid 99); 2 Jul 2009 18:50:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Jul 2009 18:50:31 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of thadguidry@gmail.com designates 209.85.219.216 as permitted sender) Received: from [209.85.219.216] (HELO mail-ew0-f216.google.com) (209.85.219.216) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Jul 2009 18:50:22 +0000 Received: by ewy12 with SMTP id 12so2654678ewy.11 for ; Thu, 02 Jul 2009 11:50:01 -0700 (PDT) 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; bh=0juGCm1sKtPelL1xkyfFCphpQ5h7Ju0JAY1qqkbz22I=; b=prRmyixkhLwRrEfa0JvLSJtYrfLS+PaQP+ggNFSk5bPVViwX8H7ldeuBwxkKlr3Nzf yPe127q/131hlBbbxkfJVExEwbWrYxj+sJDsegFOp72n0VjqDH3xhxh77lvYGhV7C1kk +qXkl2MKlWAvx1s7l41j2wCSGm/jssmtTeXR4= 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; b=YAJWqQ/JMAvYb63R3CuyW7kIDrBaBQR1MUKM2cvoPeoeVbFV+ucyqCeGUiKIGIpRqE OzjaH5tdgByiWfGKiFsWWAUF7AthDCSbcQGg9as5Owbqj/y9gQU2ye2p+M1wkhQb2EK5 iQKKSOU3FLMPYRVYqzANaCdlWirn/8E89Olo0= MIME-Version: 1.0 Received: by 10.211.166.2 with SMTP id t2mr452620ebo.49.1246560601833; Thu, 02 Jul 2009 11:50:01 -0700 (PDT) In-Reply-To: <3418A46D-FE98-4782-9D5A-D45DE1FD899D@apache.org> References: <3418A46D-FE98-4782-9D5A-D45DE1FD899D@apache.org> Date: Thu, 2 Jul 2009 13:50:01 -0500 Message-ID: Subject: Re: Timetable for 0.10.0 From: Thad Guidry To: dev@couchdb.apache.org Content-Type: multipart/alternative; boundary=0015174c3f0cdd043a046dbd8163 X-Virus-Checked: Checked by ClamAV on apache.org --0015174c3f0cdd043a046dbd8163 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit My feedback would be: Were those features worthy of waiting for? If the larger community has a need for those features, then perhaps it was best to wait? Although CouchDB dev may be trying to emulate similar approaches such as Fedora and Ubuntu with quick release cycles for the sake of growth of the project? Is that your thinking, Damien? - pushed from the sidelines of project development. -Thad On Thu, Jul 2, 2009 at 12:45 PM, Damien Katz wrote: > I think we plan on doing a 0.10.0 release within the next month or so, as > it's been 3+ months since we did 0.9.0. > > We shouldn't worry about what features are ready, we should just pick a > date to make a 0.10.x branch and then no new features go into the branch > after that, just bug fixes. If it's not in trunk at that time, then it's not > in the branch. We wait a week or so to see if any bugs are found, patch the > branch as we go. Once we have a stable branch, then we release 0.10.0. > > I propose Friday, July 31st as the 0.10.x branch date. I don't care that > much about the exact, but I do want to pick a date and stick with it, > because I don't want to get into the same situation we did with 0.9.0, where > it was held up for months as we waited way too long for features I was > working on. (sorry) > > All feedback welcome. > > -Damien > --0015174c3f0cdd043a046dbd8163--