Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:94707 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 13585 invoked from network); 25 Jul 2016 15:36:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Jul 2016 15:36:30 -0000 Authentication-Results: pb1.pair.com smtp.mail=anatol.php@belski.net; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=anatol.php@belski.net; sender-id=unknown Received-SPF: error (pb1.pair.com: domain belski.net from 85.214.73.107 cause and error) X-PHP-List-Original-Sender: anatol.php@belski.net X-Host-Fingerprint: 85.214.73.107 klapt.com Received: from [85.214.73.107] ([85.214.73.107:41341] helo=h1123647.serverkompetenz.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 03/91-04402-BF136975 for ; Mon, 25 Jul 2016 11:36:28 -0400 Received: by h1123647.serverkompetenz.net (Postfix, from userid 1006) id 70DC3782F66; Mon, 25 Jul 2016 17:36:24 +0200 (CEST) Received: from w530phpdev (pD9FD2BF6.dip0.t-ipconnect.de [217.253.43.246]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by h1123647.serverkompetenz.net (Postfix) with ESMTPSA id 2B0B1782F66; Mon, 25 Jul 2016 17:36:22 +0200 (CEST) To: "'Christoph Becker'" , "'Davey Shafik'" Cc: , "'Ferenc Kovacs'" References: <37ae91bd-6f07-c14b-faeb-b7ba246c43db@gmx.de> <029001d1e641$c359f3d0$4a0ddb70$@belski.net> In-Reply-To: Date: Mon, 25 Jul 2016 17:36:19 +0200 Message-ID: <046e01d1e68a$4bd76e20$e3864a60$@belski.net> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQE+7pgpC6AMO53Hp9POOD4QWbU8ewGmPKpHAZpu0fcB0AoT3KEmlV4Q Content-Language: en-us Subject: RE: [PHP-DEV] Bundled SQLlite3 From: anatol.php@belski.net ("Anatol Belski") > -----Original Message----- > From: Christoph Becker [mailto:cmbecker69@gmx.de] > Sent: Monday, July 25, 2016 10:30 AM > To: Davey Shafik ; Anatol Belski = > Cc: internals@lists.php.net; Ferenc Kovacs > Subject: Re: [PHP-DEV] Bundled SQLlite3 >=20 > On 25.07.2016 at 09:11, Davey Shafik wrote: >=20 > > I'd like to see an updated SQLite in 7.1, this is part of shoring up > > the stability of the release IMO. >=20 > Thanks, Anatol and Davey for the fast reply. >=20 > After having a closer look at the release news, it seems that there = have been no > major bugs in 3.8.10.2, and that release is not so old (2015-05-20), = so I leave 5.6 > and 7.0 as is. >=20 For 7.0 it should be fine as well, I guess. I just meant it's usually = enough to ask the RM of the lowest branch, as then it'll have to be = merged up anyway. Thanks Anatol > 7.1 and master should, however, be fixed (i.e. update of sqlite3.h and > sqlite3ext.h to 3.13.0). Done with src/commit/ee07e23>. >=20 > I'll try to keep an eye on SQLite3 wrt. new releases and possibly = necessary > updates in PHP. >=20 > > On Sun, Jul 24, 2016 at 11:57 PM, Anatol Belski > > > > wrote: > > > >> Hi Christoph, > >> > >>> -----Original Message----- > >>> From: Christoph Becker [mailto:cmbecker69@gmx.de] > >>> Sent: Monday, July 25, 2016 12:49 AM > >>> To: internals@lists.php.net > >>> Subject: [PHP-DEV] Bundled SQLlite3 > >>> > >>> Hi! > >>> > >>> What's our stance on updating the bundled SQLite3? > >>> > >>> Currently the PHP-5.6 and 7.0 branch have 3.8.10.2, while the > >>> PHP-7.1 and master branch have 3.9.2 (sqlite3.h) respectively = 3.13.0 > (sqlite3.c). > >> The latter > >>> would have certainly to be fixed to be consistent, but I have some > >>> doubts regarding sticking with old SQLite3 versions for supported > >>> PHP > >> versions. After all, > >>> all minor versions at least as of SQLite 3.9.0 are "regularly > >>> scheduled maintenance releases"[1], and it appears that no = bug-fixes > >>> will be > >> published for > >>> non-current minor versions. > >>> > >> Normally it is ok to upgrade the bundled libsqlite. When done > >> carefully, even in the stable branch. Fe from the news you've = linked > >> - "Yikes! The > >> 3.12.0 and 3.12.1 releases contain a backwards compatibility bug!" = :) > >> But similar situations already happened before. However not = upgrading > >> it at all for 3 years is also not good, so fine with upgrading it = from time to > time. > >> A respective RM should be better asked for approval. > >> > >> Regards > >> > >> Anatol >=20 > -- > Christoph M. Becker >=20 > -- > PHP Internals - PHP Runtime Development Mailing List To unsubscribe, = visit: > http://www.php.net/unsub.php