rfc:experimental
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
rfc:experimental [2014/10/28 18:57] – krakjoe | rfc:experimental [2017/09/22 13:28] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 26: | Line 26: | ||
Any code that is merged with an existing user base depending on it | Any code that is merged with an existing user base depending on it | ||
cannot be marked as experimental. | cannot be marked as experimental. | ||
+ | | ||
+ | New code, with no user base, can be considered experimental for a | ||
+ | maximum of 2 years. | ||
- | New code, with no user base, can be considered experimental for a maximum of 1 year. | + | This allows the definition to apply to SAPI and extension code, and further clarifies what we can consider experimental, and for how long. |
- | + | ||
- | This allows the definition to apply to SAPI and extension code, and further clarifies what we can consider experimental. | + | |
===== 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 // |
rfc/experimental.1414522632.txt.gz · Last modified: 2017/09/22 13:28 (external edit)