rfc:backwards_compatibility

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
rfc:backwards_compatibility [2011/09/25 01:25] – fix title alan_krfc:backwards_compatibility [2011/09/25 01:39] – [When can BC be broken] alan_k
Line 45: Line 45:
  
  
-===== When an BC   be broken =====+===== When can BC   be broken =====
  
   * Class A - At any time.   * Class A - At any time.
   * Class B - Must have have a consensus among developers (normally by RFC/vote).   * Class B - Must have have a consensus among developers (normally by RFC/vote).
-  * Class C - Must pass the some basic tests+  * Class C - Must pass the some basic tests (voting is essential)
      * Does it affect a number of end users (eyeball / grep various open source projects, PEAR, Syphony, Zend and various CMS / large open source projects)      * Does it affect a number of end users (eyeball / grep various open source projects, PEAR, Syphony, Zend and various CMS / large open source projects)
      * Can a "Forward Compatility workaround" be implemented by end users trivially based on a Depreciation warning.      * Can a "Forward Compatility workaround" be implemented by end users trivially based on a Depreciation warning.
rfc/backwards_compatibility.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1

Page Tools