From dev-return-48910-archive-asf-public=cust-asf.ponee.io@couchdb.apache.org Wed Dec 4 06:08:35 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 3DCB6180656 for ; Wed, 4 Dec 2019 07:08:35 +0100 (CET) Received: (qmail 67897 invoked by uid 500); 4 Dec 2019 06:08:34 -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 67885 invoked by uid 99); 4 Dec 2019 06:08:33 -0000 Received: from Unknown (HELO mailrelay1-lw-us.apache.org) (10.10.3.159) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Dec 2019 06:08:33 +0000 Received: from [192.168.1.42] (69-196-165-48.dsl.teksavvy.com [69.196.165.48]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id 9F29F4FB3 for ; Wed, 4 Dec 2019 06:08:33 +0000 (UTC) Subject: Re: CouchDB 3.0 Update - Dec 3rd To: dev@couchdb.apache.org References: From: Joan Touzet Organization: Apache Software Foundation Message-ID: Date: Wed, 4 Dec 2019 01:08:33 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Deni, Is it wise to rush out a 3.0 release prior to the holidays? I don't think so. Practically speaking we have 2 weeks before people start disappearing (including me, I'm gone as of Dec 18) and I don't think we'll get either the critical mass for testing, nor the attention from our release channels, if we rush to get it done before then. Consider this an informal desire to push off the RC/release process until January 2020. If the rest of the PMC want to push ahead (knowing I won't be here to help, and are ready to do it themselves), go for it. -Joan On 2019-12-04 12:47 a.m., Jan Lehnardt wrote: >  >> On 4. Dec 2019, at 05:32, Denitsa Burroughs wrote: >> >> Hi all, >> >> We are really close to merging the last few open PRs for CouchDB 3.0. I'd >> like to propose that we aim to merge all remaining changes *by the end of >> the week* (Dec 6th) and work on a first RC next week. Please let me know if >> you don't think you could meet that goal. Also, last call for any >> additional change requests! >> Here's the current status: >> >> *In progress:* >> - 2167 Remove vestiges of view-based `_changes` feed >> *(Eric) **- PR reviewed, >> addressing comments* >> - 1875 Update SpiderMonkey version >> *(Peng Hui)* *- PR >> reviewed, addressing comments* >> - 2171 Document new management subsystems (smoosh, ioq, ken) >> -ioq left. *(Adam) **- ioq >> only, doc ticket, not a blocker* >> - 1524 Per-document access control #1524 >> *(Jan)* - >> *Need an ETA* > > Def not before Christmas, but as stated, happy to leave this for 3.1 or later. EXCEPT for one patch to accept the _access member in docs. > > Im travelling internationally until the end of *next* week, so I can't promise that before Dec 13. > > It is a relatively minor patch, though, so we might be okay with sneaking it during the RC phase. > > Best > Jan > — > >> - 2249 Cluster setup does not create IOQ stats database >> *(Adam) **- ETA Dec 6 * >> >> *Backlog:* >> *- *2191 Tighten up security model >> *- **(TBD)** change db >> security to admin_only, small change* >> - Release Notes >> - Blog posts (see Jan's email) >> >> Thanks! >> >> Deni >