Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:73513
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.182 as permitted sender)
MIME-Version: 1.0
Sender: julienpauli@gmail.com
Date: Wed, 2 Apr 2014 13:33:56 +0200
Message-ID: <CAMUwpuQZrHBVkipgfbtaPxwUqGBGoX=AgAJrzXWCS5GATQcsbA@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=bcaec547c9d554f29904f60dab01
Subject: Branching PHP6
From: jpauli@php.net (Julien Pauli)

--bcaec547c9d554f29904f60dab01
Content-Type: text/plain; charset=ISO-8859-1

Hey ,

We've been talking about PHP6 for several weeks now.

From what I understand, we agreed on :

- We must release a new major version, ASAP I'd say
- It should be named "PHP6"
- It should break BC where needed, and introduce new concepts
- The main concept to concentrate on is Unicode implementation
- All ideas have been grouped at https://wiki.php.net/ideas/php6
- We go for a 2 year developpment iteration


All in one, 5.6 is going to be released in few months, and we now must
concentrate on PHP6.

For this, there are two needs :
- Start writing RFCs, PHP6 specific, and start debating ideas on an
"official" basis (RFCs + mail discussions)
- Branch PHP6 , so that we can start hacking and get more motivations.

Thoughts about how/when to branch PHP6 ?


Julien Pauli

--bcaec547c9d554f29904f60dab01--