Return-Path: 
 <dev-return-28418-apmail-couchdb-dev-archive=couchdb.apache.org@couchdb.apache.org>
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 CEB4D10F1F
	for <apmail-couchdb-dev-archive@www.apache.org>;
 Thu, 18 Jul 2013 14:37:39 +0000 (UTC)
Received: (qmail 14583 invoked by uid 500); 18 Jul 2013 14:37:39 -0000
Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org
Received: (qmail 14456 invoked by uid 500); 18 Jul 2013 14:37:39 -0000
Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@couchdb.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@couchdb.apache.org>
List-Post: <mailto:dev@couchdb.apache.org>
List-Id: <dev.couchdb.apache.org>
Reply-To: dev@couchdb.apache.org
Delivered-To: mailing list dev@couchdb.apache.org
Received: (qmail 14439 invoked by uid 99); 18 Jul 2013 14:37:38 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Jul 2013 14:37:38 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=5.0
	tests=RCVD_IN_DNSWL_NONE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of djc.ochtman@gmail.com
 designates 209.85.192.174 as permitted sender)
Received: from [209.85.192.174] (HELO mail-pd0-f174.google.com)
 (209.85.192.174)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Jul 2013 14:37:33 +0000
Received: by mail-pd0-f174.google.com with SMTP id 10so3161754pdc.33
        for <multiple recipients>; Thu, 18 Jul 2013 07:37:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:in-reply-to:references:from:date
         :x-google-sender-auth:message-id:subject:to:cc:content-type;
        bh=IcN6lnYkR3ff53T8K5iewby/aOFaYGDKnWV5K4H81AU=;
        b=OG4lUdSkroHg53JNO8GmQ16yRbzyA6fLNXDblBzuTCQRqrOy+fO8GzqbgM1Bhz0q+3
         up1oOrQQwCJrNjGw8BHtq4HvmkIQ+0gd8lwIPbzAs0nC0qlRSqfeti8DwPLLPbqMn8bQ
         j86MXwBHFfx85eXK4wcbcm6300vwTF+oX7pN23SDEvw7nVFmSpZ7QHRDF8lmKn+m3UXe
         NaW3qNQVghooVhkiQUjjksmpQ+yaISrEfz/Ffq4gd/5xDiQsWXqa9IfQt416ajj8sij5
         20C4RM225DezF+iUaaRRqkXlKyzs2OVSpw+aIOYs/XgjMb0ynxhN6uJmTLZXWvF+yzTb
         2VYg==
X-Received: by 10.68.107.226 with SMTP id hf2mr12569050pbb.28.1374158232699;
 Thu, 18 Jul 2013 07:37:12 -0700 (PDT)
MIME-Version: 1.0
Sender: djc.ochtman@gmail.com
Received: by 10.70.19.139 with HTTP; Thu, 18 Jul 2013 07:36:52 -0700 (PDT)
In-Reply-To: 
 <CAJNb-9q9f26wxM25vxxw1MX00CFisB6xrKf+-dO6+=QLa8BHpw@mail.gmail.com>
References: <3675f22c8ce44f7c9037b883686a10d3@git.apache.org>
 <7e60d841fd5f4534ab557ba7acc25453@git.apache.org>
 <CAJNb-9q9f26wxM25vxxw1MX00CFisB6xrKf+-dO6+=QLa8BHpw@mail.gmail.com>
From: Dirkjan Ochtman <dirkjan@ochtman.nl>
Date: Thu, 18 Jul 2013 16:36:52 +0200
X-Google-Sender-Auth: MO3ALHpBUqhWu3oB3Nl9TjfVJZ4
Message-ID: 
 <CAKmKYaB6A5yoZ7pOX3EUO8Sgd89F2GMMvXqMMh4cnFe6z2svZw@mail.gmail.com>
Subject: Re: [2/3] git commit: updated refs/heads/master to 6ad181c
To: "dev@couchdb.apache.org" <dev@couchdb.apache.org>
Cc: commits@couchdb.apache.org
Content-Type: text/plain; charset=UTF-8
X-Virus-Checked: Checked by ClamAV on apache.org

On Thu, Jul 18, 2013 at 4:32 PM, Benoit Chesneau <bchesneau@gmail.com> wrote:
> I'm not sure what prompted the urgency of this change but the vote was
> aborted until we find a way to generate the new changelog correctly and
> keep the old one.
>
> Note that I quite like to have the changes available on the doc (though it
> could be duplicated to the root too), so not sure now that it's done what
> should be done.

Okay, sorry for rushing that a bit.

I wasn't clear on the timeline for Robert's email about retracting the
point for 1.4. From reading the messages again, I don't really
understand why we'd want to keep NEWS and CHANGES around. For me as a
RM, keeping three places in sync is just a stupid chore, and I'd
prefer not to deal with it. If people feel strongly about it, I'll
happily re-add NEWS and/or CHANGES with contents populated based on
what we accumulate in the docs.

Cheers,

Dirkjan