rfc:php53eol

Differences

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

Link to this comparison view

rfc:php53eol [2012/11/29 11:32]
pajoye [Introduction]
rfc:php53eol [2013/02/07 22:16] (current)
nikic Close vote, RFC is accepted
Line 3: Line 3:
   * Date: 2012-03-02   * Date: 2012-03-02
   * Author: Pierre Joye <​pierre@php.net>​   * Author: Pierre Joye <​pierre@php.net>​
-  * Status: ​Under Discussion+  * Status: ​Accepted
   * First Published at: http://​wiki.php.net/​rfc/​php53eol   * First Published at: http://​wiki.php.net/​rfc/​php53eol
  
 ===== Introduction ===== ===== Introduction =====
  
-The purpose of this RFC is to define when PHP 5.3 serie won'​t ​be supported ​anymore+The purpose of this RFC is to define when the PHP 5.3 series will no longer ​be supported.
  
 As PHP 5.3 was released before the new release process was defined and implemented,​ we have to define a clear EOL ((End of Life)). As PHP 5.3 was released before the new release process was defined and implemented,​ we have to define a clear EOL ((End of Life)).
  
-===== Option 1 =====+Even if the 5.3 release manager already stated something about the status of PHP 5.3, it is critical for us to have a clear and open decision. PHP 5.3 is still the most widely (maintained) branch and many projects rely on it as a minimum version. It is also important to keep in mind that we won't have this problem anymore in 5.4 or later and the life cycle is already clearly defined by the [[rfc/​releaseprocess|release process RFC]]. ​  
 +===== Two years: one normal fixes and one security fixes only =====
  
-One year with bugs fixes followed by one year with security fixes only+One year with bug fixes followed by one year with security fixes only.
  
-==== Pros ====+Security issues cover only bugs marked as security issues or defined as such by the PHP Security team.
  
-==== Cons ==== 
  
-===== Option 2 ===== 
  
-Two years with security fixes only+===== Two years with security fixes only =====
  
-==== Pros ====+Two years with security fixes only. Security issues cover only bugs marked as security issues or defined as such by the PHP Security Team.
  
-==== Cons ====+===== One year with normal and security fixes =====
  
-===== Option 3 =====+One year with bug fixes (both security and normal bugs).
  
-One year with bugs fixes (both security and normal bugs) +===== One year with security fixes only =====
- +
-==== Pros ==== +
- +
-==== Cons ====+
  
-===== Option 4 =====+One year with security fixes only.
  
-One year with security fixes only 
  
-==== Pros ====+===== Vote ===== 
 +<doodle  
 +title="​Which EOL period should we choose?"​ auth="​pajoye"​ voteType="​single"​ closed="​true">​ 
 +   * Two years, one normal fixes and one security fixes only, announce with the next 5.3 release 
 +   * Two years, one normal fixes and one security fixes only, announce with 5.5 final release 
 +   * Two years with security fixes only, announce with the next 5.3 release 
 +   * Two years with security fixes only, announce with 5.5 final release 
 +   * One year with normal and security fixes, announce with the next 5.3 release 
 +   * One year with normal and security fixes, announce with 5.5 final release 
 +   * One year with security fixes only, announce with the next 5.3 release 
 +   * One year with security fixes only, announce with 5.5 final release 
 +</​doodle>​
  
 ==== Cons ==== ==== Cons ====
Line 46: Line 51:
 ===== Changelog ===== ===== Changelog =====
  
-* 2012/03/02: adding "​Pros/​Cons"​ sections to help future discussion+  * 2013/01/08: Final draft 
 +  ​* 2012/03/02: adding "​Pros/​Cons"​ sections to help future discussion
rfc/php53eol.txt · Last modified: 2013/02/07 22:16 by nikic