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 34E6AB3C0 for ; Mon, 16 Jan 2012 11:26:50 +0000 (UTC) Received: (qmail 49420 invoked by uid 500); 16 Jan 2012 11:26:49 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 49306 invoked by uid 500); 16 Jan 2012 11:26:48 -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 49298 invoked by uid 99); 16 Jan 2012 11:26:47 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Jan 2012 11:26:47 +0000 Received: from localhost (HELO mail-iy0-f180.google.com) (127.0.0.1) (smtp-auth username rnewson, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Jan 2012 11:26:47 +0000 Received: by iaby26 with SMTP id y26so2017385iab.11 for ; Mon, 16 Jan 2012 03:26:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.42.161.10 with SMTP id r10mr10298045icx.22.1326713206796; Mon, 16 Jan 2012 03:26:46 -0800 (PST) Received: by 10.42.6.72 with HTTP; Mon, 16 Jan 2012 03:26:46 -0800 (PST) In-Reply-To: References: <4F0D9E99.5030505@gmail.com> <4F0DF5DF.7080808@gmail.com> Date: Mon, 16 Jan 2012 11:26:46 +0000 Message-ID: Subject: Re: RFC: Releasing 1.2.0 From: Robert Newson To: dev@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I merged master so I can't be positive which commit is the fix yet but this one looks likely: https://github.com/cmullaparthi/ibrowse/commit/e05aa73f1acbfe877f7f0b6214f5= 72b5a42b3db8 B. On 16 January 2012 01:09, Filipe David Manana wrote: > On Sunday, January 15, 2012, Robert Newson wrote: >> I'd say it's too late for the ibrowse fix but we should pick it up for 1= .3 > > Can you point us to what that ibrowse fix is (e.g. Github commit link)? > As far as I can see there are no fixes upstream that we don't have in 1.2= .x > Thanks > >> >> B. >> >> On 15 January 2012 21:31, Noah Slater wrote: >>> I await your feedback. >>> >>> On Sun, Jan 15, 2012 at 7:46 PM, Robert Newson > wrote: >>> >>>> If it's a regression, before. If not, after. >>>> >>>> B. >>>> >>>> On 15 January 2012 19:40, Noah Slater wrote: >>>> > Are we going to punt on a Windows binary, Dave? >>>> > >>>> > On Sun, Jan 15, 2012 at 7:05 PM, Dave Cottlehuber >>>> wrote: >>>> > >>>> >> On 15 January 2012 19:05, Noah Slater wrote: >>>> >> > Bump. Dave? Gonna move without if you don't speak up. :) >>>> >> >>>> >> Sorry!! Literally *just* finished looking at this. >>>> >> >>>> >> TL;DR - let's roll 1.2.0. >>>> >> >>>> >> I don't see any *functional* issues in the failures from the test >>>> >> suite - attachments are written, and read, correctly. For some as y= et >>>> >> unknown reason the MD5 is different on Windows vs Linux & Mac OS, b= ut >>>> >> this has been present for some time. It's only turned up =A0as a re= sult >>>> >> of additional tests applied in COUCHDB-1337. >>>> >> >>>> >> The underlying crypto:md5 values are the same, and so is the raw HT= TP >>>> >> data. I am still digging through mochi to where this comes from. >>>> >> >>>> >> I don't see any issues for replication - can anybody confirm? This >>>> >> looks like a dev issue rather than user impacting. >>>> >> >>>> >> from 1.1.1_js-1.8.0: >>>> >> 12> Digest =3D base64:encode(Digest_Binary). >>>> >> <<"jeLnIuUvK7d+6gya044lVA=3D=3D">> >>>> >> >>>> >> from 1.2.x: >>>> >> 8> Digest =3D base64:encode(Digest_Binary). >>>> >> <<"jeLnIuUvK7d+6gya044lVA=3D=3D">> >>>> >> >>>> >> A+ >>>> >> Dave >>>> >> >>>> >> > > -- > Filipe David Manana, > > "Reasonable men adapt themselves to the world. > =A0Unreasonable men adapt the world to themselves. > =A0That's why all progress depends on unreasonable men."