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 74D3A4099 for ; Sat, 4 Jun 2011 09:17:36 +0000 (UTC) Received: (qmail 14841 invoked by uid 500); 4 Jun 2011 09:17:35 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 14516 invoked by uid 500); 4 Jun 2011 09:17:35 -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 14488 invoked by uid 99); 4 Jun 2011 09:17:35 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Jun 2011 09:17:35 +0000 Received: from localhost (HELO [192.168.1.41]) (127.0.0.1) (smtp-auth username nslater, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Jun 2011 09:17:35 +0000 Subject: Re: [DRAFT FOR REVIEW] [ACTION REQUIRED] www.apache.org/dist/ housekeeping Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Noah Slater In-Reply-To: <13db01cc2296$a0a776b0$e1f66410$@16degrees.com.au> X-Noah: Awesome Date: Sat, 4 Jun 2011 10:17:32 +0100 Cc: infrastructure-private@apache.org, board@apache.org, dev@couchdb.apache.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <4D7888D4.8050309@apache.org> <4DB80719.10903@apache.org> <4DE95770.1010504@apache.org> <13db01cc2296$a0a776b0$e1f66410$@16degrees.com.au> To: private@couchdb.apache.org X-Mailer: Apple Mail (2.1084) CCing dev@ again, as some non-PMC members will be interested. On 4 Jun 2011, at 10:06, Gavin McDonald wrote: > You have 0.11.0, 0.11.1 and 0.11.2 all of the same release line, you = only > need 0.11.2 with the > other two older releases being available in the archives area should = anyone > want those. We have historically kept these releases on the downloads page so that = people have a migration path from the original point release through to = the most recent bugfix release, should that be needed. (This also helps = people understand what has been fixed/changed since the original point = release.) As far as I understand, we cannot continue to advertise these = on our downloads page if they are archived, because we would not be able = to make use of the Apache mirrors. > Note that every release fixes bugs ;) Sure, but only point releases add new features. So calling them bugfix releases is a decent way to highlight their = purpose. :P