Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:69073 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 85145 invoked from network); 12 Sep 2013 02:46:10 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Sep 2013 02:46:10 -0000 Authentication-Results: pb1.pair.com smtp.mail=rasmus@lerdorf.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=rasmus@lerdorf.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.192.172 cause and error) X-PHP-List-Original-Sender: rasmus@lerdorf.com X-Host-Fingerprint: 209.85.192.172 mail-pd0-f172.google.com Received: from [209.85.192.172] ([209.85.192.172:36161] helo=mail-pd0-f172.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 19/F0-12981-1FA21325 for ; Wed, 11 Sep 2013 22:46:10 -0400 Received: by mail-pd0-f172.google.com with SMTP id z10so10070509pdj.31 for ; Wed, 11 Sep 2013 19:46:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=z/SvX7oVCfdc+dtQ0cVTXv803v+T73pevGMIQyp4+UA=; b=Yvr4ssy3+uY9N9oGdRklHvm5xffMhCRMsAn7Lahh/0wMIcqDl2hFfWx+sFdTlbC0hC TSLSo+nnMlrM6rDvlc+OvwPJLgXH23DdK6HJ92rbIG9NYMQmUC9QmOtsGxamW9KmAwJI Mm7P50rz7Sw35E76RnPTvuhfPYr4OWwWlH2wDcWAnrVD62WjBvTdCD04gSbDflfQTIV8 bVueZsrvwmHhkDU/2w2TPD/Mp6pT9gcYr+hh13HyFEX49muXy2F58KlHAeitFosc2nib xloFemCLYzVq6jje4fmpimPBKq5geS2OGJtAtaD8gICN8QphBNe4sOwvSXdkM2d8xvix XV8w== X-Gm-Message-State: ALoCoQmqEy6vAiLP4P82tmSuwQO4hNMkFmjTidfZrRsTcmUmGUBPnaeGTOMOdyFu2QoTYBWN4HK8 X-Received: by 10.68.232.134 with SMTP id to6mr553459pbc.163.1378953965663; Wed, 11 Sep 2013 19:46:05 -0700 (PDT) Received: from [192.168.200.14] (c-50-131-44-225.hsd1.ca.comcast.net. [50.131.44.225]) by mx.google.com with ESMTPSA id b4sm1291433pbc.22.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 11 Sep 2013 19:46:05 -0700 (PDT) Message-ID: <52312AEB.7070904@lerdorf.com> Date: Wed, 11 Sep 2013 22:46:03 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8 MIME-Version: 1.0 To: Florin Patan CC: PHP Internals References: <1378903588.3917.54.camel@guybrush> <5230B28A.40707@oracle.com> In-Reply-To: X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Wake up From: rasmus@lerdorf.com (Rasmus Lerdorf) On 09/11/2013 05:34 PM, Florin Patan wrote: > - lack of a clear roadmap: as I said earlier, can someone really tell > what's in the next two versions of php from now That's never going to happen. We don't have paid developers that we can assign tasks to. We have volunteers who work on things they need or find fun to work on. We can't possibly provide a solid road map two (I assume you mean major) versions out. The process is clearly described here: https://wiki.php.net/rfc/releaseprocess When it comes time to do the next release we look at the state of the various projects/rfcs and we, led by the released manager, decide which features are far enough along to go into that release. Saying that a certain feature will be in a release 2 years from now without knowing whether the person championing it will still be around just isn't realistic. Plus interesting ideas come up all the time, and a solid 2-year road map would mean there would be at least a 2-year delay on anything new. We do have a fuzzy road map in the form of the set of RFCs on the wiki. A subset of those are likely to be in the next release. And to influence that, instead of writing lots of long email threads on internals, contact the author of the RFC you are interested in and ask them if they need help with anything. And yes, even very complete RFCs may still get shot down for a number of different reasons. PHP is quite mature, and major new features are going to face a lot of friction. This is not a bad thing. I often wish that some of the things I put in years ago had had a bit more friction. But there was nobody around to provide that friction. Now we have the luxury of a lot of experienced people with a wealth of ideas and opinions to provide this friction. -Rasmus