Return-Path: Delivered-To: apmail-incubator-couchdb-dev-archive@locus.apache.org Received: (qmail 3762 invoked from network); 12 Jun 2008 19:46:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Jun 2008 19:46:46 -0000 Received: (qmail 76234 invoked by uid 500); 12 Jun 2008 19:46:48 -0000 Delivered-To: apmail-incubator-couchdb-dev-archive@incubator.apache.org Received: (qmail 76207 invoked by uid 500); 12 Jun 2008 19:46:48 -0000 Mailing-List: contact couchdb-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: couchdb-dev@incubator.apache.org Delivered-To: mailing list couchdb-dev@incubator.apache.org Delivered-To: moderator for couchdb-dev@incubator.apache.org Received: (qmail 62438 invoked by uid 99); 12 Jun 2008 19:38:08 -0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Message-Id: <8929A878-BEBA-49F0-A3D2-EB304E10A0D5@jaguNET.com> From: Jim Jagielski To: couchdb-dev@incubator.apache.org In-Reply-To: <91F34915-03F0-40AF-BA98-54711280B648@sauria.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v924) Subject: Re: [VOTE] Apache CouchDB 0.8.0-incubating release Date: Thu, 12 Jun 2008 15:37:36 -0400 References: <20080610201835.GG26134@bytesexual.org> <71FCC6D8-2440-446D-876D-66C59AA37F3A@gmail.com> <150D6C1E-0D8B-4458-BF00-DD3E6153FF81@sauria.com> <20080611193130.GL26134@bytesexual.org> <91F34915-03F0-40AF-BA98-54711280B648@sauria.com> X-Mailer: Apple Mail (2.924) X-Virus-Checked: Checked by ClamAV on apache.org On Jun 11, 2008, at 5:50 PM, Ted Leung wrote: > > On Jun 11, 2008, at 12:31 PM, Noah Slater wrote: > >> On Wed, Jun 11, 2008 at 11:46:18AM -0700, Ted Leung wrote: >>> 1. I don't see any NOTICES file - there should be an entry for >>> MochiWeb >> >> Oh damn. What should I do to prepare a new release. Do I have to >> cut 0.8.1 and >> open a new VOTE? > > Well, I don't know that we need a new release number, since stuff > didn't go up on the distribution servers, but once the files are > fixed, we probably do need another vote. I don't know what Jim > and Gianugo think. > Version numbers are cheap, so a 0.8.1 is probably safest.