Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:80256 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 76379 invoked from network); 7 Jan 2015 20:45:21 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Jan 2015 20:45:21 -0000 Authentication-Results: pb1.pair.com header.from=francois@tekwire.net; sender-id=softfail Authentication-Results: pb1.pair.com smtp.mail=francois@tekwire.net; spf=softfail; sender-id=softfail Received-SPF: softfail (pb1.pair.com: domain tekwire.net does not designate 212.27.42.2 as permitted sender) X-PHP-List-Original-Sender: francois@tekwire.net X-Host-Fingerprint: 212.27.42.2 smtp2-g21.free.fr Received: from [212.27.42.2] ([212.27.42.2:18423] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C8/C0-03551-0EA9DA45 for ; Wed, 07 Jan 2015 15:45:21 -0500 Received: from moorea (unknown [82.240.16.115]) by smtp2-g21.free.fr (Postfix) with ESMTP id 61D884B010F; Wed, 7 Jan 2015 21:43:18 +0100 (CET) Reply-To: To: "'Leigh'" , "'Scott Arciszewski'" Cc: "'inter >> PHP internals'" References: In-Reply-To: Date: Wed, 7 Jan 2015 21:45:11 +0100 Message-ID: <00a101d02aba$d4ef4a80$7ecddf80$@tekwire.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Content-Language: fr Thread-Index: AQJJNtCO4+uCMGzvhfm5zMc2thSKqAIRgHYum7J55FA= X-Antivirus: avast! (VPS 150107-0, 07/01/2015), Outbound message X-Antivirus-Status: Clean Subject: RE: [PHP-DEV] Idea for PHP.net From: francois@tekwire.net (=?utf-8?Q?Fran=C3=A7ois_Laupretre?=) > De : Leigh [mailto:leight@gmail.com] >=20 > On 7 January 2015 at 12:52, Scott Arciszewski > wrote: > > > > Would it be possible for php.net to publish a cryptographically = signed > > (e.g. openssl_sign() with a RSA private key kept offline) list in a > > pre-defined location (e.g. /stable_versions.txt) so that scripts can = be > > written to read (and cache) the latest stable versions? >=20 > I already do something similar to this for some of my CI, ensuring > tests pass on new versions of PHP. >=20 > I use the following shell script snippet to check for new versions (If > there's a diff I parse the output with PHP to find _which_ new > version) >=20 > git ls-remote -t https://github.com/php/php-src | cut -d '/' -f3 | > grep -P '^php-5\.\d+\.\d+' | sort -V And what about extracting the information you require via the github API = ? Exploring the release information for the 'php/php-src' project, you = would get all the information you need. Once you know the names of every = available releases, it is quite easy to determine if your current = version needs upgrading. You can even display how many days passed since = the last stable release, how many days your version is late, etc. I am = not a specialist but github can probably provide the security level you = require. Regards, Fran=C3=A7ois