Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAJ_m3YCb4DHxD-fJ3dHqd9Cfwih=px+e-+-iG4LJJtHcyZMmGw@mail.gmail.com>
References: 
 <CA+Y+445CgtW7Ftx+hgvVnc4Cv-=7uRSwLFL6Q=J0kgKM2xourA@mail.gmail.com>
 <CA+Y+445yg0D9SAYT_kGanfCmQE2jDhBMbrjssPEonjgwHs=3dA@mail.gmail.com>
 <CABvT1DFKaDnCa8mbiS0E36ae+HVCPVB42v2Xfsxodw0oEy41xQ@mail.gmail.com>
 <CA+Y+445DLF=HeWWAm6np0MpfDKy7rz7SAYnD3PE3AauH1eMEkg@mail.gmail.com>
 <0BB4F003-4C8B-441A-9CEF-08782AF170BB@dionne-associates.com>
 <CA+Y+446EzWOveYYHs3HZnrtZrUJ5VcVuk63QOtJ3p4yBbN54uw@mail.gmail.com>
 <AA97DC79-7D23-4681-9FA5-0A7901B013EC@dionne-associates.com>
 <-4709298919342606669@unknownmsgid>
 <CAJNb-9regswTwBE4Frh2X-m=eopN1TqGzd7wBSxx2Xqvjd6EQA@mail.gmail.com>
 <CAJ_m3YDxiXPCnhGOJwMJrZH8WRuW_bx+RiV0Mi1FvZ-DesOLOA@mail.gmail.com>
 <CA+Y+446AJD=vyFOMVeR3tF=kPCZNzzwd0aDnLLjU2EgLJYYn=g@mail.gmail.com>
 <CAHZBNKbqKB-jq0tjYoLfXBEGp8O8ZL-ZmiFu8_UfqwX_-grXiw@mail.gmail.com>
 <CA+Y+446zHtdQCyEyXNN1vva_g680u8MzqLNPtyF2mSzeHcu0dA@mail.gmail.com>
 <CAJ_m3YCb4DHxD-fJ3dHqd9Cfwih=px+e-+-iG4LJJtHcyZMmGw@mail.gmail.com>
From: Jason Smith <jhs@iriscouch.com>
Date: Wed, 14 Mar 2012 09:47:53 +0700
Message-ID: 
 <CAN-3CBKNH2Deo+PuL84C6mXqSHFBiUTvejUJJnLewNOj_rqAJg@mail.gmail.com>
Subject: Re: 1.2.0 status update
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

IMHO:

It affects advanced users, with multiple JS builds installed. It is
not a 1.2.0 blocker. It's not relevant to this discussion.

In the meantime, I have been prepping all the Linux VMs I can find to
test for the next 1.2.0 vote.

On Wed, Mar 14, 2012 at 8:59 AM, Paul Davis <paul.joseph.davis@gmail.com> w=
rote:
> On Tue, Mar 13, 2012 at 8:27 PM, Noah Slater <nslater@tumbolia.org> wrote=
:
>> Thanks Dave.
>>
>> On Tue, Mar 13, 2012 at 11:20 PM, Dave Cottlehuber <dave@muse.net.nz> wr=
ote:
>>>
>>> What's the plan to move forwards here? We are damn close but a half
>>> finished solution for 1426 will
>>> simply mean another round. This needs more collaboration so that we
>>> are not working async on this.
>>>
>>
>> I don't think we are damn close.
>>
>> We've seen hardly any progress with this issue during the week and a hal=
f
>> since Beno=C3=AEt took ownership of it. That tells me that it can't be v=
ery
>> important, and so I will attempt another vote tomorrow, with or without =
it.
>>
>> If someone, anyone, wants to land a fix for it between now and then, be =
my
>> guest. But I will not hold the release up any longer for an issue that
>> nobody can be bothered to fix.
>>
>> (Not to discredit the work already put in to it. I really appreciate tha=
t.
>> Seriously, I do. But it's obviously not important enough to block the
>> release any longer, or it would've been fixed already. Actions speak lou=
der
>> than words.)
>
> While I appreciate your enthusiasm, you appear to have not been
> following the issue very closely. There have been two versions of
> Benoit's initial work in the last week with multiple test reports [1].
> The current issue is that Dave has a machine that has a broken
> configuration. We need to figure out if we want to dig deeper into
> that or just assume that it's a broken configuration and thus outside
> our control. Once we have a decision there we can either commit
> Benoit's latest patch or fix it up to hack around that last edge case.
>
>
> [1] https://issues.apache.org/jira/browse/COUCHDB-1426


--=20
Iris Couch