Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:99879
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain basereality.com from 209.85.192.182 cause and error)
MIME-Version: 1.0
Date: Mon, 17 Jul 2017 16:12:19 +0200
Message-ID: <CA+kxMuTFNzu=UAL_41CeW=M9DDjpfS4Ujz6gBee4MwxU34CvaA@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Bundled libraries upgrade 'process'
From: danack@basereality.com (Dan Ackroyd)

Hi Internals,

I just investigated an alleged bug related to the SQLite3 extension.
It seems this bug occurs when PHP is compiled with the current bundled
SQLite files, which are a little out of date as they are version:
"3.15.1", date: "2016-11-04".

Listed at https://sqlite.org/changes.html there are multiple versions
that SQLite could be upgraded to.

* 2016-11-28 (3.15.2) - small bugfix upgrade.
* 2017-06-08 (3.19.3) - bigger upgrade that has performance improvements.

Questions:

1. Do we have a process for deciding whether to upgrade bundled libraries?

2. Can anyone see anything in the release notes that would be a
problem for upgrading past 3.15.2 ?

3. Do we have a process for getting feedback from users about whether
a proposed upgrade would cause problems, other than doing the upgrade
and shipping it?

I can't see anything listed in the SQLite release notes that would
cause a problem.....but that's obviously not the same as being sure an
upgrade wouldn't cause problems.

cheers
Dan
Ack