Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68113 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 26930 invoked from network); 13 Jul 2013 14:03:28 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Jul 2013 14:03:28 -0000 Authentication-Results: pb1.pair.com smtp.mail=johannes@schlueters.de; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=johannes@schlueters.de; sender-id=unknown Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error) X-PHP-List-Original-Sender: johannes@schlueters.de X-Host-Fingerprint: 217.114.211.66 config.schlueters.de Received: from [217.114.211.66] ([217.114.211.66:39775] helo=config.schlueters.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 7A/E4-58645-E2E51E15 for ; Sat, 13 Jul 2013 10:03:27 -0400 Received: from [192.168.2.20] (ppp-188-174-58-89.dynamic.mnet-online.de [188.174.58.89]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by config.schlueters.de (Postfix) with ESMTPSA id B912365B6C; Sat, 13 Jul 2013 16:03:23 +0200 (CEST) To: Sebastian Bergmann Cc: internals@lists.php.net In-Reply-To: <51E07D5A.3090409@php.net> References: <51E07D5A.3090409@php.net> Content-Type: text/plain; charset="UTF-8" Date: Sat, 13 Jul 2013 16:03:16 +0200 Message-ID: <1373724196.2394.2542.camel@guybrush> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] "Zend Engine v2.5.0-dev" in PHP 5.5.0 From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) On Sat, 2013-07-13 at 00:04 +0200, Sebastian Bergmann wrote: > Zend Engine v2.5.0-dev, Copyright (c) 1998-2013 Zend Technologies > > At the end of the day it is just a version number but it looks > "unprofessional". Would be nice if things like this did not happen. Yes, mistakes happen, as you can see by commit 184dea this was already noticed and fixed. I think there also hand been bug reports about it. But well, nothing we can change for5.5.0 as that's out .. johannes