Newsgroups: php.doc,php.internals Path: news.php.net Xref: news.php.net php.doc:969384814 php.internals:71207 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 16197 invoked from network); 17 Jan 2014 14:12:13 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Jan 2014 14:12:13 -0000 Authentication-Results: pb1.pair.com smtp.mail=adam@adamharvey.name; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=adam@adamharvey.name; sender-id=pass Received-SPF: pass (pb1.pair.com: domain adamharvey.name designates 209.85.223.173 as permitted sender) X-PHP-List-Original-Sender: adam@adamharvey.name X-Host-Fingerprint: 209.85.223.173 mail-ie0-f173.google.com Received: from [209.85.223.173] ([209.85.223.173:51873] helo=mail-ie0-f173.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 92/00-16023-C3A39D25 for ; Fri, 17 Jan 2014 09:12:12 -0500 Received: by mail-ie0-f173.google.com with SMTP id e14so5327772iej.18 for ; Fri, 17 Jan 2014 06:12:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=adamharvey.name; s=google; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; bh=Y3jsCUSwrK1sdC6hleCczELeb4rhQ+KHCalzaI/PUB8=; b=o4uizewm+ltri3XYe4/rObrKqwDcrppsY0dBcfWs6FU/Xk3RmVvuHuyD+Zz73Cqk/A NBOoM5lPoN/ezi3MIGK0LkpZ+U5XfZP4486fsZpXUY7ETBWgnJmj1MNZhCzclEJ0FuBy 3+zJ1E8izSVx38y5gDVvst6xqlli8EuXzjLBw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=Y3jsCUSwrK1sdC6hleCczELeb4rhQ+KHCalzaI/PUB8=; b=Mu4YxlCM/QzcYwTi16mPm8Up7jVeIyzzicuSlNZE0R7mgaI0l1CiGLxgcE6W9c+ETH DYh4/fZUMSN6pbA9NcLwMTPBvNXEiQcVsqVNK/B/b4NnR7n3FrjmzBHDfv0RAHEB8qQ3 RlayMg7oHMwUB0isioh9v1UE+rXZrT30xoH3e3CtSMr2S2BoU369J+yj/98jcI84KVyx kz23Cfp3a4aA0fsPSIsJ81hZ/3fdlnOqUnuQ8aRsME2EP7INwn6E/PMMdNx7wxT2uiHS wINtjE0KRQ2ub9jth2UdxjbMpQ/8oTiNdCFXM2BL0MvXhUKEN4TSG/2YJzZvd6OtPia+ X8xw== X-Gm-Message-State: ALoCoQmJ5qQo+rFcWj+6hfUyAfZ9Gu0sS4alpavRR4AuBv7lMFn2wpk9MopaqLtghpH/5RXrF9gy X-Received: by 10.50.29.49 with SMTP id g17mr2629367igh.35.1389967929445; Fri, 17 Jan 2014 06:12:09 -0800 (PST) MIME-Version: 1.0 Sender: adam@adamharvey.name Received: by 10.42.206.208 with HTTP; Fri, 17 Jan 2014 06:11:49 -0800 (PST) In-Reply-To: References: Date: Fri, 17 Jan 2014 22:11:49 +0800 X-Google-Sender-Auth: sMlhBmpK9ue1EIA2TXgW7b5wB_o Message-ID: To: Ferenc Kovacs Cc: PHP Internals , phpdoc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] Proposed timetable for PHP 5.6.0 From: aharvey@php.net (Adam Harvey) On 17 January 2014 17:05, Ferenc Kovacs wrote: > On Wed, Jan 15, 2014 at 4:33 PM, Ferenc Kovacs wrote: >> I plan to tag the the first alpha today, and release it tomorrow, so the >> time for new RFCs are almost up. > > I had to recreate my dev environment as my home desktop got some hardware > issues, and I didn't wanted to tag the release without a bit more testing= . > Hopefully I can tag the release today, and I will talk with Julien and th= e > windows build guys about the next possible release date. > > Sorry for the delay! I'm quite happy about the delay, as it's allowed me to use a Friday evening productively hacking together a skeletal draft of the PHP 5.6 migration guide =E2=80=94 it's not on the mirrors yet, but it is on docs.php.net: http://docs.php.net/manual/en/migration56.php. At this stage, 5.6 features aren't being documented outside of the migration guide, since we're not at the feature freeze yet, so some of the new features are only minimally documented. (For instance, there are many variations of splat and variadic syntax that aren't covered at present.) Once we hit feature freeze, they'll start getting proper pages/sections in the language reference and will have more comprehensive documentation (particularly if you help write it). For developers who've committed significant code to 5.6, please make sure your feature/deprecation/change is mentioned somewhere in there =E2=80= =94 if it hasn't been, it's almost certainly because it wasn't in UPGRADING, so please fix that. :) Please also feel free to jump in and edit anything you're unhappy with! Some of the smaller changes were a bit opaque. Thanks, Adam, who really doesn't want to spend the eventual 5.6.0 release day the way he spent the 5.5.0 release day.