rfc:experimental
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
rfc:experimental [2014/10/28 18:54] – krakjoe | rfc:experimental [2014/10/28 19:04] – krakjoe | ||
---|---|---|---|
Line 27: | Line 27: | ||
cannot be marked as experimental. | cannot be marked as experimental. | ||
| | ||
- | New code, with no user base, can be considered experimental for a maximum of 1 year. | + | New code, with no user base, can be considered experimental for a maximum of 2 years. |
- | This allows the definition to apply to SAPI and extension code, and further clarifies what we can consider experimental. | + | This allows the definition to apply to SAPI and extension code, and further clarifies what we can consider experimental, and for how long. |
===== Staging Process for Experimental Code ===== | ===== Staging Process for Experimental Code ===== | ||
Experimental code can be developed in an experimental branch of php-src or an external repository. | Experimental code can be developed in an experimental branch of php-src or an external repository. | ||
+ | |||
+ | Experimental does not mean unstable; every effort should be made to stabilize code before merging is suggested. | ||
Before any merges into production or development branches of php-src, maintainers of experimental code must invite discussion on internals, for // | Before any merges into production or development branches of php-src, maintainers of experimental code must invite discussion on internals, for // | ||
Line 40: | Line 42: | ||
Only if there are no objections to a merge from internals after a period of 7 days, a merge to production or development branches is permitted after discussion with release manager(s) has taken place. | Only if there are no objections to a merge from internals after a period of 7 days, a merge to production or development branches is permitted after discussion with release manager(s) has taken place. | ||
- | |||
- | This allows experimental code to be developed at a different pace to production or development branches of PHP, but still requires that the maintainers are in communication with internals. | ||
After the defined period for experimental code has passed, the experimental notice must be removed and the code subject to the normal internals process. | After the defined period for experimental code has passed, the experimental notice must be removed and the code subject to the normal internals process. | ||
+ | |||
+ | This allows experimental code to be developed at a different pace to production or development branches of PHP, but still requires that the maintainers are in communication with internals. | ||
===== Proposed Voting Choices ===== | ===== Proposed Voting Choices ===== |
rfc/experimental.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1