| aharvey | Yes | 2014-11-21 18:01 |
| ajf | Yes | 2014-11-21 08:37 |
| andrey | Yes | 2014-11-21 16:21 |
| auroraeosrose | Yes | 2014-11-22 17:16 |
| bwoebi | Yes | 2014-11-21 09:33 |
| davey | Yes | 2014-11-21 17:04 |
| derick | Yes | 2014-11-21 10:47 |
| dmitry | Yes | 2014-11-24 09:32 |
| dragoonis | Yes | 2014-11-24 13:08 |
| googleguy | Yes | 2014-11-21 18:08 |
| guilhermeblanco | Yes | 2014-11-21 15:42 |
| gwynne | Yes | 2014-11-24 09:47 |
| hywan | Yes | 2014-11-24 08:58 |
| jedibc | No | 2014-11-23 10:48 |
| jwage | Yes | 2014-11-22 16:55 |
| kalle | Yes | 2014-11-22 12:53 |
| klaussilveira | Yes | 2014-11-21 13:43 |
| krakjoe | Yes | 2014-11-21 08:12 |
| kriscraig | No | 2014-11-23 00:02 |
| laruence | Yes | 2014-11-21 14:30 |
| leigh | Yes | 2014-11-21 10:23 |
| lstrojny | Yes | 2014-11-27 16:27 |
| mbeccati | Yes | 2014-11-22 08:43 |
| mike | Yes | 2014-11-21 08:30 |
| mrook | Yes | 2014-11-22 11:42 |
| nikic | Yes | 2014-11-27 17:31 |
| patrickallaert | Yes | 2014-11-25 09:24 |
| pollita | Yes | 2014-11-27 17:15 |
| ramsey | Yes | 2014-11-22 14:24 |
| rasmus | Yes | 2014-11-24 07:38 |
| reeze | Yes | 2014-11-24 03:46 |
| shm | Yes | 2014-11-28 08:54 |
| stas | Yes | 2014-11-21 19:09 |
| weierophinney | Yes | 2014-11-22 14:29 |
| willfitch | Yes | 2014-11-22 03:24 |
| zeev | Yes | 2014-11-21 08:07 |
Copied from wiki.php.net, last synchronized Oct 13, 2026 11:50 UTC
With key decisions about both the version number and the engine for PHP 7 behind us, it's time to define an agreed-upon timeline so that all contributors can align around it. The purpose of this RFC is to define a one year timeline for the delivery of PHP 7.0, with a projected release date of November 2015.
As the competitive landscape for PHP is evolving, the proposal is to shorten that timeline as much as possible while still taking advantage of the unique opportunities available to us due to the major version number change. A one year timeline will allow us a fair amount of time to work on changes that are only allowed in major versions - namely, ones that break compatibility. Arguably, while we should definitely take the opportunity to implement compatibility-breaking changes in 7.0, we also shouldn't turn it into a compatibility-breaking festival, as the more we break, the more likely it is users would delay upgrades, stay with old, insecure versions - or even consider other alternative options. RFCs that don't explicitly require a major version change (i.e., ones that don't break compatibility) - can also be proposed, but they should be secondary, as they can equally make it into future minor versions (7.1, 7.2, etc.).
| Proposed Milestones |
|---|
| Milestone |
| 1. Line up any remaining RFCs that target PHP 7.0. |
| 2. Finalize implementation & testing of new features. |
| 3. Release Candidate (RC) cycles |
| 4. GA/Release |
It's worth noting that the 3rd and 4th milestones will be quality dependent. If we have evidence that suggests that PHP 7 isn't sufficiently mature to go into the RC stage in June, or GA in October - we should of course adjust the timeline accordingly, and not push out a half-baked release. However, the goal would be to stick as much as possible to the deadline of new going-into-7.0 RFCs, and strive to follow the timelines for the 2nd and 3rd milestones as much as possible, to ensure an October 2015 release of PHP 7.0.
Proposed voting choices are Yes (vote in favor of the timeline) or No (reject the timeline)
As this is not a language-changing RFC, a simple majority of 50%+1 is required to approve this RFC.
Vote: php7timeline — Yes: 34 · No: 2 (closed)