From dev-return-48915-archive-asf-public=cust-asf.ponee.io@couchdb.apache.org Thu Dec 5 19:09:58 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 5E19D180643 for ; Thu, 5 Dec 2019 20:09:58 +0100 (CET) Received: (qmail 31868 invoked by uid 500); 5 Dec 2019 19:09: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 31852 invoked by uid 99); 5 Dec 2019 19:09:57 -0000 Received: from Unknown (HELO mailrelay1-lw-us.apache.org) (10.10.3.159) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Dec 2019 19:09:57 +0000 Received: from auth2-smtp.messagingengine.com (auth2-smtp.messagingengine.com [66.111.4.228]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id 0C1384FB3 for ; Thu, 5 Dec 2019 19:09:57 +0000 (UTC) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailauth.nyi.internal (Postfix) with ESMTP id CD48D21B84 for ; Thu, 5 Dec 2019 14:09:56 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Thu, 05 Dec 2019 14:09:56 -0500 X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudekuddguddvvdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhephfgtgfgguffffhfvjgfkofesth hqmhdthhdtjeenucfhrhhomheptegurghmucfmohgtohhlohhskhhiuceokhhotgholhho shhksegrphgrtghhvgdrohhrgheqnecuffhomhgrihhnpehtihhgvghrnhgrshhsrghurd gtohhmpdhgihhthhhusgdrtghomhenucfkphepuddvledrgedurdekjedrheenucfrrghr rghmpehmrghilhhfrhhomhepkhhotgholhhoshhkodhmvghsmhhtphgruhhthhhpvghrsh honhgrlhhithihqdelkedvieegheeitddqudehheeijeejheegqdhkohgtohhlohhskhep pegrphgrtghhvgdrohhrghesfhgrshhtmhgrihhlrdgtohhmnecuvehluhhsthgvrhfuih iivgeptd X-ME-Proxy: Received: from kocolosk.cambridge.ibm.com (unknown [129.41.87.5]) by mail.messagingengine.com (Postfix) with ESMTPA id 7592880062 for ; Thu, 5 Dec 2019 14:09:56 -0500 (EST) From: Adam Kocoloski Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Re: CouchDB 3.0 Update - Dec 3rd Date: Thu, 5 Dec 2019 14:09:55 -0500 References: <89667473-2fdb-ca3d-593c-7d825e09b3eb@tigernassau.com> <18BE3096-96F8-41B3-8B1E-8C667EA83D1A@apache.org> To: dev@couchdb.apache.org In-Reply-To: Message-Id: <3D9CF2B6-BA87-4A15-ACF4-A0678665449F@apache.org> X-Mailer: Apple Mail (2.3601.0.10) Here=E2=80=99s my view: - A release should have convenience binaries available within days - We don=E2=80=99t need to have all the deep dive blog posts on the new = capabilities ready, but they should follow within weeks - I don=E2=80=99t think we need to insert code freeze delays more than = the usual window of testing for a release candidate My understanding is that one of the benefits of the new Jenkins setup is = the ability to automate many steps of the binary package generation. I = think we can devote some time to getting that online while we chase down = the last few remaining tickets and see if we can lighten the load for = binary package generation. If we can get this done in December - great! Adam > On Dec 5, 2019, at 1:34 PM, Denitsa Burroughs = wrote: >=20 > Hi all - >=20 > Thanks all for your input so far. Anyone else care to share their > preference on the release options for 3.0? >=20 > a) release in December > b) release in January > c) code freeze (now) after the required content is merged and only = allow > bug fixes through January? >=20 > Thanks! >=20 > Deni >=20 > On Wed, Dec 4, 2019 at 11:53 AM Robert Newson = wrote: >=20 >> Hi, >>=20 >> I=E2=80=99m fine with a release either side of Christmas but I agree = with Joan=E2=80=99s >> point. >>=20 >> I suggest a compromise of a code freeze. Only fixes for 3.0 to be = merged >> until the new year then do the release dance. >>=20 >>> On 4 Dec 2019, at 14:45, support-tiger = wrote: >>>=20 >>> fyi: Every year Ruby releases a new major version on Christmas - has >> become a tradition with the user base - so no need to worry about = holidays >> but obviously must be ready to ship. >>>=20 >>> Do not forget about PR - I have seen little on the web about the >> upcoming major version release. What are the major new features ? = (not >> just a changelog). How about a review from someone trying out the = beta or >> RC. >>>=20 >>> One more thing: node express crud example ? (if you want to attract >> users to a JSON database) >>>=20 >>> And one more thing: are Fedora, Debian, Ubuntu pkgs ready ? >>>=20 >>>=20 >>>> On 12/4/19 6:43 AM, Denitsa Burroughs wrote: >>>> Hi Joan, >>>>=20 >>>> Point taken. Let's see what the rest of the PMC members thinks. = Just to >> be >>>> clear: I had spoken to Bob about helping with the release = activities, >> so I >>>> wasn't expecting this to land on you. :) >>>>=20 >>>> I think that the biggest challenge would be getting the release = notes >> and >>>> documentation ready. I would appreciate some feedback on areas that = are >>>> lacking (if any) so that I can track it. Happy to open a ticket = where we >>>> could capture a list if that makes sense. >>>>=20 >>>> Thanks, >>>>=20 >>>> Deni >>>>=20 >>>>> On Wed, Dec 4, 2019 at 1:08 AM Joan Touzet = wrote: >>>>>=20 >>>>> Deni, >>>>>=20 >>>>> 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. >>>>>=20 >>>>> 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. >>>>>=20 >>>>> -Joan >>>>>=20 >>>>>> On 2019-12-04 12:47 a.m., Jan Lehnardt wrote: >>>>>> =EF=BB=BF >>>>>>> On 4. Dec 2019, at 05:32, Denitsa Burroughs < >>>>> denitsa.burroughs@gmail.com> wrote: >>>>>>> =EF=BB=BFHi all, >>>>>>>=20 >>>>>>> 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: >>>>>>>=20 >>>>>>> *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 >>>>>> =E2=80=94 >>>>>>=20 >>>>>>> - 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) >>>>>>>=20 >>>>>>> Thanks! >>>>>>>=20 >>>>>>> Deni >>>=20 >>> -- >>> Support Dept >>> Tiger Nassau, Inc. >>> www.tigernassau.com >>> 406-624-9310 >>>=20 >>>=20 >>>=20 >>=20 >>=20