Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:65141 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 85061 invoked from network); 24 Jan 2013 05:28:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Jan 2013 05:28:44 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.42 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.215.42 mail-la0-f42.google.com Received: from [209.85.215.42] ([209.85.215.42:56883] helo=mail-la0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 88/D1-65404-A86C0015 for ; Thu, 24 Jan 2013 00:28:43 -0500 Received: by mail-la0-f42.google.com with SMTP id fe20so9735542lab.1 for ; Wed, 23 Jan 2013 21:28:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=QdvOIJA12y2EicwjfxEF0JnspJh5q4TSf49xCL2LXsc=; b=gL2V5DQemrBDuV09IB2OTZdRl7waFDPMTh1JqkbO34s6FgXj94N6xU+MtxruEyiOtj NR0ac68Av9fhVy2VzVLpI58WlkUNwKLzbuPT9F3zPWjXch+ZNa4rSxq6LtY+ssfOPVX2 CUWQGqaaAPqClH+m3+uqeTEo1VIwjV967MkWU7m0ONDObor7CiqjtEi9LWQAJOhS1yBa a0gu34ntMioZHma24MDPpVXRxXB4h9J74abSmt7zY4SJQygc3lCKjsk0y4DNIbKG/Kyi mBYpKqSP2DhOz9xAa8QbwJ2ORaWIZ8j4jgVLXpraNs3Fg1Q8YT5HH81JqzYh3ld3bOeO Qf2Q== MIME-Version: 1.0 X-Received: by 10.112.44.161 with SMTP id f1mr287510lbm.29.1359005319363; Wed, 23 Jan 2013 21:28:39 -0800 (PST) Received: by 10.112.127.230 with HTTP; Wed, 23 Jan 2013 21:28:39 -0800 (PST) Received: by 10.112.127.230 with HTTP; Wed, 23 Jan 2013 21:28:39 -0800 (PST) In-Reply-To: <51008FE0.7010908@oracle.com> References: <50FDC4D8.6030105@oracle.com> <51001FE2.7090109@anderiasch.de> <51008FE0.7010908@oracle.com> Date: Thu, 24 Jan 2013 06:28:39 +0100 Message-ID: To: Christopher Jones Cc: PHP internals , Florian Anderiasch Content-Type: multipart/alternative; boundary=bcaec554d1fe4efdd004d40215a0 Subject: Re: [PHP-DEV] Re: [RFC][vote] 5.3 EOL From: pierre.php@gmail.com (Pierre Joye) --bcaec554d1fe4efdd004d40215a0 Content-Type: text/plain; charset=ISO-8859-1 Hi Chris, On Jan 24, 2013 2:35 AM, "Christopher Jones" wrote: > > > > On 01/23/2013 09:37 AM, Florian Anderiasch wrote: >> >> On 01/21/2013 11:44 PM, Christopher Jones wrote: >> >>> Pierre, >>> >>> Can you review this RFC and the votes? The wording "5.5 final >>> release" needs assessing. You probably meant "first 5.5 production >>> release". If anyone interpreted it as it is actually written >>> i.e. "terminal 5.5 release", then the vote needs to be re-run. >> >> >> How do you plan to find out who would've taken it that way? Ask all who >> voted? > > > Probably. I suggest being practical and getting a best-effort feel for it. > Lack of responses to my email is one indicator that the the community > doesn't have an issue with the RFC wording. > > >> Maybe it sounds more ambiguous for a native speaker, but I actually had >> to reread this mail to get your point. I've never heard anyone use >> "final" as "terminal", > > > I have. There is also a subtle distinction between the use of "final" in > "final 5.5.0" and "final 5.5". > > >> the "final" in the software development domain >> has always been the name for the version after the RCs, at least for me. > > > That's the way I took it for my vote. The next day I realized that non-native > English speakers might possibly have thought otherwise. I asked many native speakers and all understood it as "when 5.5.0 stable release will be announced". Cheers, Pierre --bcaec554d1fe4efdd004d40215a0--