Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 87564 invoked from network); 26 Jan 2011 12:58:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 26 Jan 2011 12:58:16 -0000 Received: (qmail 45398 invoked by uid 500); 26 Jan 2011 12:58:16 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 45053 invoked by uid 500); 26 Jan 2011 12:58:13 -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 45044 invoked by uid 99); 26 Jan 2011 12:58:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Jan 2011 12:58:12 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.9] (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 26 Jan 2011 12:58:12 +0000 Received: (qmail 87519 invoked by uid 99); 26 Jan 2011 12:57:51 -0000 Received: from localhost.apache.org (HELO [192.168.0.3]) (127.0.0.1) (smtp-auth username nslater, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Jan 2011 12:57:51 +0000 Subject: Re: [VOTE] Apache CouchDB 1.0.2 Release, Round 3 Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=windows-1252 From: Noah Slater In-Reply-To: <8EE9C841-4C83-4201-B343-34B5F88069A2@apache.org> X-Noah: Awesome Date: Wed, 26 Jan 2011 12:57:49 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <3EEE8B55-C689-4AC0-96E1-4BFFFC6B95FE@apache.org> References: <1331C7A6-7772-498B-9852-47685E3A77BE@apache.org> <8EE9C841-4C83-4201-B343-34B5F88069A2@apache.org> To: dev@couchdb.apache.org X-Mailer: Apple Mail (2.1082) On 26 Jan 2011, at 12:49, Jan Lehnardt wrote: > Do you think we can put this in the release announcement and on the = downloads page, too? =97 Sort of like a post-vote addendum to NEWS = without actually changing NEWS? Could do. Would we make it a generic recommendation for all users? No harm in updating NEWS after the release, as long as it is only = updated on the branch. However, I'm a little confused. We usually put = version number requirements in the README.=