Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 7B056200BE4 for ; Wed, 21 Dec 2016 12:05:13 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 79864160B26; Wed, 21 Dec 2016 11:05:13 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id C0F6E160B0C for ; Wed, 21 Dec 2016 12:05:12 +0100 (CET) Received: (qmail 96877 invoked by uid 500); 21 Dec 2016 11:05:11 -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 96733 invoked by uid 99); 21 Dec 2016 11:05:11 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Dec 2016 11:05:11 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 8394418051E for ; Wed, 21 Dec 2016 11:05:10 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.3 X-Spam-Level: X-Spam-Status: No, score=0.3 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id G6MuAORO2qeX for ; Wed, 21 Dec 2016 11:05:09 +0000 (UTC) Received: from monoceres.uberspace.de (monoceres.uberspace.de [95.143.172.184]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 9DF525F342 for ; Wed, 21 Dec 2016 11:05:08 +0000 (UTC) Received: (qmail 25266 invoked from network); 21 Dec 2016 11:04:57 -0000 Received: from localhost (HELO ?10.0.0.11?) (127.0.0.1) by monoceres.uberspace.de with SMTP; 21 Dec 2016 11:04:57 -0000 From: Jan Lehnardt Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Subject: Re: Publisher account for CouchDB snap Date: Wed, 21 Dec 2016 12:04:55 +0100 References: <92274ed5-e799-d0e9-03c5-c8eaa4c81cf5@gmail.com> To: dev@couchdb.apache.org In-Reply-To: Message-Id: <9A6A424B-F75F-4A60-B24C-A6547AF12173@apache.org> X-Mailer: Apple Mail (2.3251) archived-at: Wed, 21 Dec 2016 11:05:13 -0000 > On 20 Dec 2016, at 19:56, Eli Stevens (Gmail) wrote: > > On Tue, Dec 20, 2016 at 9:16 AM, Michael Hall wrote: >> On 12/19/2016 06:23 PM, Eli Stevens (Gmail) wrote: >>> I'll have some people on my team get on that as soon as we have time; >>> probably after the new year. >>> >> >> Thanks! If they have any questions or need help, I'm mhall119 in >> #couchdb-dev or they can email me directly. > > Thanks, will do. > > >> In that case, you could have your script run "snap install couchdb" and >> then copy the configuration and data files into the snap's locations > > Perfect. > > >>> - Is it possible to disable automatic updates for snaps? >> >> It's possible, I don't know the details of it though. Can you tell me >> what your concern is with leaving it on? > > The FDA requires us to produce documentation detailing the versions of > 3rd party software we use to construct our product, and attest to the > suitability of those versions for the purpose that we're using them > for. Maintaining the proper documentation gets a lot harder when the > version can get swapped out from underneath us without warning. And if > there's an actual incompatibility, that means that cancer patients > might not be able to start their course of treatment on time, which > the patients, clinical staff, and our director of customer support all > agree is undesirable. ;) > > From a practical perspective, most of our clients don't allow the > systems in their data center access to the internet anyway (our > systems have a considerable amount of medical records with patient > identifying information, so that makes sense), and I'd rather not > bifurcate the install base any more than necessary. > > >> Snaps can run on 14.04, but that's as far back as we've been able to >> support, since snapd and snap-confine depend on newer kernel features >> and systemd. And since 12.04 is going to be EOL next year, I hope you're >> planning an upgrade of those systems anyway, > > Right now, we're planning on letting hardware attrition (and resulting > replacements) drive the transition off of 12.04. I don't recall the > exact details, but we were having issues getting grub to not insist > that someone hit enter during the first boot after upgrade, which > violates our "upgrades must be headless" requirement. > > The impending EOL and unavailability of CouchDB 2.0 might cause us to > revisit that decision. The what? Best Jan -- > > >> I'd love to hear how that goes, any feedback you can give me about using >> the snap I will funnel back to the snappy development team so they can >> improve it. > > Sounds great. :) > > Cheers, > Eli -- Professional Support for Apache CouchDB: https://neighbourhood.ie/couchdb-support/