Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of msddsm@gmail.com designates
 209.85.212.52 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=date:from:subject:to:x-priority:in-reply-to:message-id:mime-version
         :content-type:content-transfer-encoding:x-mailer;
        b=JXZrI/hDDIfhJen6P/NpZd9rHhvL0I9ltWBEPZUfYcWuadc1bSUQFNybpbGUbcAEgC
         WvOYJdlorICci0X8oAizaq6thwkPs642Zh9JqGYYPup+CgOAZXTFKoHlH1NoAfKDHERe
         sxP5FhPLhYSlcgNW2bxUPrD2+f1yA50igmHmM=
Date: Mon, 15 Nov 2010 05:49:30 -0500
From: Matthew Sinclair-Day <msddsm@gmail.com>
Subject: Re: Release 1.0.2
To: dev@couchdb.apache.org
In-Reply-To: <5CF6C5E0-3CCB-49E1-84E9-5E217AD223C5@apache.org>
Message-ID: <r314Ps-1064i-C68F2E9A56474B6A88B87CEBFA3F1C8B@mocha.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable

On 11/15/10 at 7:11 PM, jan@apache.org (Jan Lehnardt) wrote:

>On 12 Nov 2010, at 20:21, Dirkjan Ochtman wrote:
>
>>On Wed, Nov 3, 2010 at 18:06, Filipe David Manana <fdmanana@apache.org> w=
rote:
>>> and done
>>
>>Oh, look, I'm back for more nagging! How are we doing on 1.0.2? Or
>>1.1, for that matter, just any release that gets me the good stuff
>>you've all been working on.
>
>JIRA lists a few open issues for 1.0.2:
>
>http://s.apache.org/couchdb-open-issues-1.0.2
>
>I started going through and closed / applied / deferred a few to my
>best judgement, but if you (everybody here) could help me squashing
>this list, we'll be good.
>
>Likewise, if you think any issue not on this list should be considered,
>set its "Fix Version" to "1.0.2" so we can have a look.
>
>Other than that, NEWS & CHANGES need to be updated, if anyone wants to
>tackle this.
>
>Cheers
>Jan

Looking at the issue list tagged for 1.0.2, I didn't see any=20
mention of fixes for chunked encoding and other things around=20
HTTP protocol support.  Are those fixes going to be in 1.0.2?

Matt