From dev-return-21470-apmail-couchdb-dev-archive=couchdb.apache.org@couchdb.apache.org Thu Mar 15 02:04:58 2012
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 42FB99CDD
for ; Thu, 15 Mar 2012 02:04:58 +0000 (UTC)
Received: (qmail 74558 invoked by uid 500); 15 Mar 2012 02:04:57 -0000
Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org
Received: (qmail 74522 invoked by uid 500); 15 Mar 2012 02:04:57 -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 74513 invoked by uid 99); 15 Mar 2012 02:04:57 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Mar 2012 02:04:57 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of nslater@tumbolia.org designates 209.85.215.52 as permitted sender)
Received: from [209.85.215.52] (HELO mail-lpp01m010-f52.google.com) (209.85.215.52)
by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Mar 2012 02:04:52 +0000
Received: by lahi5 with SMTP id i5so2797534lah.11
for ; Wed, 14 Mar 2012 19:04:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=tumbolia.org; s=google;
h=mime-version:x-originating-ip:in-reply-to:references:date
:message-id:subject:from:to:content-type;
bh=k9/yuVOnOdF7uqFd9NzHx2bja15Mm8EpEEXNK39qLtI=;
b=gNt73ckODaLu26HfGuyx1yfG0U9NYnJc+peJKIf2fw4LHSfAFUwDSPkJ9MQzZIGTrf
30Ix07+8DWYI8+N7HnO+TTWdvdFhxl8wVR2EO7fLWkKIKrZWsFWqzaUyMRiAR3dUrWTV
Gq7AsG+X94if+hJUcrrTy7r2wKJpx85pgNGIw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=mime-version:x-originating-ip:in-reply-to:references:date
:message-id:subject:from:to:content-type:x-gm-message-state;
bh=k9/yuVOnOdF7uqFd9NzHx2bja15Mm8EpEEXNK39qLtI=;
b=CiSFLIxHlYWp1y6gsF2hHqUoixKfOn9TrzB2Aas/82ZNWqt5GYnx4JH/FPdRPjzI/7
YmRnnwuT+Fbcvo17BIPQiGm2Y/BXuKSuln/U0zYmqdyUAAa1/S/+3mpx8DeosiDVb9BU
HZRc1ev8FfOVhTymJHFBlgiPebhhq1BqYwnFOz8mr5k9E/J8tqla2Rqu2flu99zGKSHW
lFKDS5BQkO95EDJB27iQJ6B2dIU2CXPLPes86sSb1kQWbNfzGEYErrfIINPcK2x03YHU
CaR3YAI1AaW/EP7m56WxvVv6IoBIm2nYkGgIo0q27/GlJkSO4Zk3MbPNFeU+CBgdzjd3
0crw==
MIME-Version: 1.0
Received: by 10.112.48.202 with SMTP id o10mr1440479lbn.25.1331777070874; Wed,
14 Mar 2012 19:04:30 -0700 (PDT)
Received: by 10.112.100.194 with HTTP; Wed, 14 Mar 2012 19:04:30 -0700 (PDT)
X-Originating-IP: [78.86.152.157]
In-Reply-To:
References:
<0BB4F003-4C8B-441A-9CEF-08782AF170BB@dionne-associates.com>
<4F60C606.5060409@83864.com>
Date: Thu, 15 Mar 2012 02:04:30 +0000
Message-ID:
Subject: Re: 1.2.0 status update
From: Noah Slater
To: dev@couchdb.apache.org
Content-Type: multipart/alternative; boundary=bcaec553ff003ac16d04bb3e832c
X-Gm-Message-State: ALoCoQkVeyZqLZNWtBhjOadQhX/jQilqQiU71vpzRAvGC5jFGKMNEHimhP1n3Ze9WuQHVNBRgqRb
X-Virus-Checked: Checked by ClamAV on apache.org
--bcaec553ff003ac16d04bb3e832c
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
I didn't ask for a promise, I asked for an expectation. I want to release.
I have been asked to delay the release. I think it is only fair to ask for
an your expectation about the length of that delay. I don't care that this
is an open source project, and that we all contribute our time for free,
and because we feel passionately about the project. That is no excuse to
expect any less from people. ETAs on release-critical blockers seem like a
perfectly reasonable request, within that context.
I am insistent because I there is a fire under my arse. Getting 1.2.0 out
as soon as possible, and with as few problems as possible, is
a critical first step towards our recovery from recent events. Can't you
feel the heat too?
On Thu, Mar 15, 2012 at 1:51 AM, Paul Davis wr=
ote:
> I'm not now nor will I ever promise when a patch is going to land.
> It'll land when its ready. Once again I enjoy your enthusiasm but I'm
> a bit confused by your insistence. We're working on it. I'm even
> fairly sure I fixed Wendall and Dave's issue tonight. Randall had a
> report on a build failure though.
>
> If other people are interested, they can try the current iteration of
> the patch by cloning the COUCHDB-1426 branch from the ASF git repo and
> building locally and reporting results on the JIRA issue. I'm pretty
> sure Randall's issue was on Linux with SpiderMonkey 1.8.5 if anyone
> has that configuration handy. And if they can get it to fail it would
> be super dandy to ping me with a login to a machine that repro's.
> (I'll even screen share whilst debugging in case people want to
> watch).
>
> On Wed, Mar 14, 2012 at 12:23 PM, Noah Slater
> wrote:
> > We've waited just shy of two weeks now. How long before a fix lands? If
> > you're proposing that we delay the release again, I need to know by how
> > much you plan to delay the release. Looking at Paul and Beno=EEt here.
> >
> > On Wed, Mar 14, 2012 at 4:23 PM, Wendall Cada
> wrote:
> >
> >> +1 On what Benoit says.
> >>
> >> I'll be using the current iteration of this patch to update the couchd=
b
> >> rpm spec I've been working on. Additionally, I've opened a dialog with
> the
> >> Redhat package maintainer about the possibility of maintaining or
> >> contributing to this package for RHEL/Centos and Fedora. This can be a=
n
> >> issue for any distribution package maintainer.
> >>
> >> Wendall
> >>
> >>
> >> On 03/13/2012 09:04 PM, Benoit Chesneau wrote:
> >>
> >>> On Tue, Mar 13, 2012 at 7:47 PM, Jason Smith
> wrote:
> >>>
> >>>> 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.
> >>>>
> >>> It is. If you reread the ticket it appears that the problem is more
> >>> important than expected and I hesitated a lot to let it as blocker
> >>> like it was initially. Since the release have been postponed, we aslo
> >>> have the perfect opportunity to really fix that issue.
> >>>
> >>> Lot of our users are complaining to have some problem installing
> >>> couchdb on their machine. This isn't new. This isn't solved.
> >>>
> >>> While the lazy solution was to direct them to couchbase stuff, or
> >>> these days to build_couchdb or rcouch, I would really prefer we fix
> >>> this *important* issue and let people choose if they prefer to instal=
l
> >>> via a vendor or the official *distribution*. Last iteration of the
> >>> patch fix most of the cases I guess. We can choose like said above to
> >>> use this version and fix latest issues in next minor release or tryin=
g
> >>> to solve that last one. At this point, after different iterations,
> >>> feedback is appreciated and that is the main reason why updates of th=
e
> >>> tickets are sent to the ml.
> >>>
> >>>
> >>> - benoit
> >>>
> >>
> >>
>
--bcaec553ff003ac16d04bb3e832c--