rfc:template

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
rfc:template [2014/04/10 22:33]
levim Group Impact sections
rfc:template [2020/06/28 18:09] (current)
girgias Update version number to 8
Line 23: Line 23:
  
 ===== Introduction ===== ===== Introduction =====
-The elevator pitch for the RFC.+The elevator pitch for the RFC. The first paragraph of this section will be slightly larger to give it emphasis; please write a good introduction.
  
 ===== Proposal ===== ===== Proposal =====
Line 32: Line 32:
  
 Remember that the RFC contents should be easily reusable in the PHP Documentation. Remember that the RFC contents should be easily reusable in the PHP Documentation.
 +
 +If applicable, you may wish to use the language specification as a reference.
  
 ===== Backward Incompatible Changes ===== ===== Backward Incompatible Changes =====
Line 37: Line 39:
  
 ===== Proposed PHP Version(s) ===== ===== Proposed PHP Version(s) =====
-List the proposed PHP versions that the feature will be included in.  Use relative versions such as "next PHP 5.x" or "next PHP 5.x.y".+List the proposed PHP versions that the feature will be included in.  Use relative versions such as "next PHP 8.x" or "next PHP 8.x.y".
  
-===== Other Impact =====+===== RFC Impact =====
 ==== To SAPIs ==== ==== To SAPIs ====
 Describe the impact to CLI, Development web server, embedded PHP etc. Describe the impact to CLI, Development web server, embedded PHP etc.
Line 45: Line 47:
 ==== To Existing Extensions ==== ==== To Existing Extensions ====
 Will existing extensions be affected? Will existing extensions be affected?
 +
 +==== To Opcache ====
 +It is necessary to develop RFC's with opcache in mind, since opcache is a core extension distributed with PHP.
 +
 +Please explain how you have verified your RFC's compatibility with opcache.
  
 ==== New Constants ==== ==== New Constants ====
Line 64: Line 71:
  
 ===== Future Scope ===== ===== Future Scope =====
-This sections details areas where the feature might be improved in future, but that are not currently proposed in this RFC.+This section details areas where the feature might be improved in future, but that are not currently proposed in this RFC.
  
 ===== Proposed Voting Choices ===== ===== Proposed Voting Choices =====
 Include these so readers know where you are heading and can discuss the proposed voting options. Include these so readers know where you are heading and can discuss the proposed voting options.
- 
-State whether this project requires a 2/3 or 50%+1 majority (see [[voting]]) 
  
 ===== Patches and Tests ===== ===== Patches and Tests =====
Line 77: Line 82:
  
 Make it clear if the patch is intended to be the final patch, or is just a prototype. Make it clear if the patch is intended to be the final patch, or is just a prototype.
 +
 +For changes affecting the core language, you should also provide a patch for the language specification.
  
 ===== Implementation ===== ===== Implementation =====
 After the project is implemented, this section should contain  After the project is implemented, this section should contain 
-  - the version(s) it was merged to+  - the version(s) it was merged into
   - a link to the git commit(s)   - a link to the git commit(s)
   - a link to the PHP manual entry for the feature   - a link to the PHP manual entry for the feature
 +  - a link to the language specification section (if any)
  
 ===== References ===== ===== References =====
rfc/template.1397169225.txt.gz · Last modified: 2017/09/22 13:28 (external edit)