Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
MIME-Version: 1.0
In-Reply-To: <514B964B.9040700@apache.org>
References: 
 <CAPaJBx4cjUX7shSf7TDJgBgRTWTwMRYA7BxjutveiEh5x1S0QQ@mail.gmail.com>
	<514B4FC0.5000809@83864.com>
	<CAPaJBx4s+6kDwgjHLJC2yJ7+RwPX03-xU-z0ua-r56L5H9eMNA@mail.gmail.com>
	<514B938F.6090700@apache.org>
	<CAPaJBx7nEaPMGV9UD7X=tpmQ-f6=tyGr2y9k4XS6BVqmQ5=zyg@mail.gmail.com>
	<514B964B.9040700@apache.org>
Date: Fri, 22 Mar 2013 18:07:30 +0000
Message-ID: 
 <CAPaJBx5kHpi0OsqpRnakxeAeYL8wsZNFU7N-f-PyRHYPYBEQBg@mail.gmail.com>
Subject: Re: [DISCUSS] Prepare Apache CouchDB 1.2.2-rc.1
From: Noah Slater <nslater@apache.org>
To: "dev@couchdb.apache.org" <dev@couchdb.apache.org>
Content-Type: multipart/alternative; boundary=e89a8f646d1520c9c904d88754b9

--e89a8f646d1520c9c904d88754b9
Content-Type: text/plain; charset=ISO-8859-1

Are we all set here?


On 21 March 2013 23:22, Wendall Cada <wendallc@apache.org> wrote:

> On 03/21/2013 04:17 PM, Noah Slater wrote:
>
>> Yes, there should be an item in CHANGES. (On all branches.)
>>
> Ok, I'll add this to CHANGES for both right now.
>
>
>> Also, does this need to be applied to more than just 1.2.x, 1.3.x, and
>> master?
>>
> I've not seen this behavior in 1.0.x, I have in 1.1.x however. This is a
> harmless patch for both 1.0.x and 1.1.x. Thoughts?
>
>> See list of current releases:
>>
>> http://wiki.apache.org/**couchdb/CurrentReleases<http://wiki.apache.org/couchdb/CurrentReleases>
>>
>>
>> On 21 March 2013 23:11, Wendall Cada <wendallc@apache.org> wrote:
>>
>>  Patch has been applied to 1.2.x. Everything is good from my perspective.
>>> I
>>> could add something to CHANGES about this, but I'm not certain it's
>>> worthy
>>> of noting. Let me know if this is necessary, I'll be glad to add
>>> comments.
>>>
>>> Wendall
>>>
>>>
>>> On 03/21/2013 11:26 AM, Noah Slater wrote:
>>>
>>>  When you say "added", do you mean the patch should be applied to the
>>>> 1.2.x
>>>> branch?
>>>>
>>>>
>>>> On 21 March 2013 18:21, Wendall Cada <wendallc@83864.com> wrote:
>>>>
>>>>   https://issues.apache.org/******jira/browse/COUCHDB-1449<https://issues.apache.org/****jira/browse/COUCHDB-1449>
>>>> <https**://issues.apache.org/**jira/**browse/COUCHDB-1449<https://issues.apache.org/**jira/browse/COUCHDB-1449>
>>>> >
>>>>
>>>>> <https**://issues.apache.org/**jira/**browse/COUCHDB-1449<http://issues.apache.org/jira/**browse/COUCHDB-1449>
>>>>> <htt**ps://issues.apache.org/jira/**browse/COUCHDB-1449<https://issues.apache.org/jira/browse/COUCHDB-1449>
>>>>> >>should
>>>>>
>>>>> be added to 1.2.2, this was a blocker for 1.3.0, but somehow was
>>>>>
>>>>> missed.
>>>>>
>>>>> Wendall
>>>>>
>>>>>
>>>>> On 03/21/2013 08:51 AM, Noah Slater wrote:
>>>>>
>>>>>   Dear community,
>>>>>
>>>>>> I would like to propose that we prepare Apache CouchDB 1.2.2-rc.1.
>>>>>>
>>>>>> The project aims to produce time-based releases. If your favourite
>>>>>> feature
>>>>>> is not ready for this version, it can be included in the next version.
>>>>>> However, if you know of anything that should block the release, please
>>>>>> speak up now.
>>>>>>
>>>>>> The 1.2.2 NEWS entry as it stands:
>>>>>>
>>>>>>     * Fixed rewrite counter bug.
>>>>>>
>>>>>> The 1.2.2 CHANGES entry as it stands:
>>>>>>
>>>>>>
>>>>>> https://git-wip-us.apache.org/******repos/asf?p=couchdb.git;a=****<https://git-wip-us.apache.org/****repos/asf?p=couchdb.git;a=**>
>>>>>> <https://git-wip-us.apache.**org/**repos/asf?p=couchdb.git;**a=**<https://git-wip-us.apache.org/**repos/asf?p=couchdb.git;a=**>
>>>>>> >
>>>>>> blob_plain;&f=CHANGES;hb=1.2.****x<https://git-wip-us.apache.****
>>>>>> org/repos/asf?p=couchdb.git;a=****blob_plain;&f=CHANGES;hb=1.**2.x<
>>>>>> https://git-wip-us.apache.**org/repos/asf?p=couchdb.git;a=**
>>>>>> blob_plain;&f=CHANGES;hb=1.2.x<https://git-wip-us.apache.org/repos/asf?p=couchdb.git;a=blob_plain;&f=CHANGES;hb=1.2.x>
>>>>>> **>
>>>>>> **>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Are these accurate? Please double check any work you may have done and
>>>>>> make
>>>>>> sure that the corresponding NEWS and CHANGES entries are up-to-date.
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>
>


-- 
NS

--e89a8f646d1520c9c904d88754b9--