rfc:php7_57_roadmap
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
rfc:php7_57_roadmap [2014/08/16 04:43] – pajoye | rfc:php7_57_roadmap [2017/09/22 13:28] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 12: | Line 12: | ||
- | ===== Proposal | + | ===== Proposals |
As this time there are two positions about when we should try to release php 7 final: | As this time there are two positions about when we should try to release php 7 final: | ||
- | * within a year, no php 5.7 | + | * within a year |
- | * within 1.5 years, with 5.7 | + | * within 1.5 years |
+ | * Whether or not to have a 5.7 release | ||
- | ===== One and a half year development and no 5.7 ===== | + | ==== PHP 7, within one year maximum |
- | * no risk to reproduce what happened with the php 6 | + | === Introduction === |
- | * Keep our limited resources on one release | + | |
- | * There are enough new features | + | 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 |
+ | |||
+ | |||
+ | === Proposal === | ||
+ | |||
+ | 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. | ||
+ | RFCs that don't explicitly require | ||
+ | |||
+ | |||
+ | ^ Proposed Milestones ^^^ | ||
+ | ^ Milestone | ||
+ | | 1. **Line up any remaining RFCs that target PHP 7.0.** | ||
+ | | 2. **Finalize implementation & testing of new features.** | Mar 16 - Jun 15 (3 months) | | | ||
+ | | 3. **Release Candidate (RC) cycles** | ||
+ | | 4. **GA/ | ||
+ | |||
+ | |||
+ | It's worth noting that the 3rd and 4th milestones will be quality dependent. | ||
+ | |||
+ | |||
+ | ==== PHP 7, within one and a half year maximum ==== | ||
+ | |||
+ | === Introduction === | ||
PHP 6 was one of the biggest trauma in the php.net history. We have magisterially failed to define a clear roadmap, to find consensus on what it should be along many other issues like small groups fighting each other or hidden meetings or developments. | PHP 6 was one of the biggest trauma in the php.net history. We have magisterially failed to define a clear roadmap, to find consensus on what it should be along many other issues like small groups fighting each other or hidden meetings or developments. | ||
Line 29: | Line 52: | ||
Most of these issues have been solved or can be solved with the RFC process. However the increasing pressure on PHP from the various alternative implementations (hhvm on top) puts us in a difficult position, and we may better have to act quickly to provide a better or similar alternative. | Most of these issues have been solved or can be solved with the RFC process. However the increasing pressure on PHP from the various alternative implementations (hhvm on top) puts us in a difficult position, and we may better have to act quickly to provide a better or similar alternative. | ||
- | ===== One and year development and 5.7 ===== | + | === Proposal |
- | * Major versions are an unique opportunity to cleanup our code base | + | |
- | * Major versions dictate what PHP will be in the next decade or more | + | |
- | * It is unrealistic to consider than less than a year is enough to understand, stabilize and release a phpng based major version. | + | |
- | * There are a couple of major features that are long due, RFCs are in progress | + | |
The release process clearly defines how a release development phase should be done. Being strict allows us to actually release any version in time, as planed. A clear roadmap defining until when RFCs can be proposed, when they have to be implemented and merged, etc prevents any delay. | The release process clearly defines how a release development phase should be done. Being strict allows us to actually release any version in time, as planed. A clear roadmap defining until when RFCs can be proposed, when they have to be implemented and merged, etc prevents any delay. | ||
Line 40: | Line 59: | ||
There are also a couple of features not twenty that are long due. For example, big integer supprt, AST, other like getter/ | There are also a couple of features not twenty that are long due. For example, big integer supprt, AST, other like getter/ | ||
+ | |||
+ | Also the idea here is not to force us to release in one and half year, there is no reason to wait if we are ready. But we cannot afford to post pone release releases dates as it always leads to more delay, again and again, recent additions like opcache in 5.5 shows it. 5 months later than planed, and it was " | ||
This is why it is critical, if not vital, to do not hurry up and be sure we do it right. | This is why it is critical, if not vital, to do not hurry up and be sure we do it right. | ||
+ | |||
+ | Keys point: | ||
+ | * Major versions are an unique opportunity to cleanup our code base | ||
+ | * Major versions dictate what PHP will be in the next decade or more | ||
+ | * It is unrealistic to consider than less than a year is enough to understand, stabilize and release a phpng based major version. | ||
+ | * There are a couple of major features that are long due, RFCs are in progress | ||
+ | |||
+ | |||
+ | |||
+ | === Timetable === | ||
+ | * Dev and beta allow new features to be added, if accepted via RFCs. | ||
+ | * RC means no new feature, even if accepted via RFCs. | ||
+ | * Anything not stable enough for the 1st RC, or blocking for final, may be removed from the release, based on core devs decision (maybe quick votes and such, consensus or RMs decision for smaller features) | ||
+ | < | ||
+ | Version Time -> | ||
+ | | ||
+ | | ||
+ | | | ||
+ | Dev | ||
+ | 1st beta |++++++++++++++++++++++++ | ||
+ | RCs 7 |+++++++++++++++++++++++++++++ | ||
+ | 5.7RC (*) | ||
+ | 5.7final | ||
+ | 7 final (*) | ||
+ | </ | ||
+ | |||
+ | === PHP 5.7 === | ||
+ | |||
+ | The idea of a PHP 5.7 is: | ||
+ | * Prepare our users to 7 | ||
+ | * No or very little additions, development must be focused on 7 | ||
+ | * Keep to our release process | ||
+ | |||
+ | It is clear that we may need a 5.7 to add the necessary notices or deprecation notices to prepare our users to move to 7. We also have to be strict and realistic about what we want in 5.7. One of the fears is that we will waste our precious resources on 5.7 instead of 7. It will not happen if we are very clear about 5.7 goals, prepare to 7. | ||
+ | |||
===== Proposed PHP Version(s) ===== | ===== Proposed PHP Version(s) ===== |
rfc/php7_57_roadmap.1408164221.txt.gz · Last modified: 2017/09/22 13:28 (external edit)