From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id D8AB56DE0355 for ; Tue, 9 May 2017 11:49:16 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.005 X-Spam-Level: X-Spam-Status: No, score=-0.005 tagged_above=-999 required=5 tests=[AWL=0.006, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rBbqjF9Sj6DQ for ; Tue, 9 May 2017 11:49:16 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 112CB6DE0352 for ; Tue, 9 May 2017 11:49:15 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.84_2) (envelope-from ) id 1d8ABH-0008Gn-Jl; Tue, 09 May 2017 14:48:19 -0400 Received: (nullmailer pid 25740 invoked by uid 1000); Tue, 09 May 2017 18:49:08 -0000 From: David Bremner To: Daniel Kahn Gillmor , Jeffrey Stedfast , "notmuch@notmuchmail.org" Cc: notmuch@freelists.org Subject: RE: Upcoming GMime 3.0 changes In-Reply-To: <87shkeklpi.fsf@fifthhorseman.net> References: <87mvcom1z8.fsf@tethera.net> <87k25q178l.fsf@tesseract.cs.unb.ca> <87shkeklpi.fsf@fifthhorseman.net> Date: Tue, 09 May 2017 15:49:08 -0300 Message-ID: <871srx27dn.fsf@tesseract.cs.unb.ca> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 May 2017 18:49:16 -0000 Daniel Kahn Gillmor writes: > > out of curiosity, why do you think we won't be able to drop gmime-2.6 > for a few years? if it's due to the debian release cycle and wanting to > backport notmuch to stretch, i don't think i'd mind providing backports > of gmime 3.0 for that purpose. That was what I was thinking about (and other distros with similar release cycles). But even among our own developers I don't know we can just throw a switch and say "install gmime 3.0 before you git pull". I guess the other point is even with backports, there is still the issue of security support for older releases. We'll need to maintain the 2.6 stuff in a branch, even if it only gets security/severe bug updates. Another question is how long Jeff plans to support 2.6 with bug fixes. d