rfc:releaseprocess

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:releaseprocess [2011/06/21 03:27]
sebastian
rfc:releaseprocess [2017/09/22 13:28] (current)
Line 3: Line 3:
   * Date: 2010-11-22   * Date: 2010-11-22
   * Author: Felipe Pena, Etienne Kneuss, Stanislav Malyshev, Gustavo André dos Santos Lopes, David Soria Parra, Christian Stocker, Rob Richards, Pierre Joye, Zeev Suraski, Ilia Alshanetsky   * Author: Felipe Pena, Etienne Kneuss, Stanislav Malyshev, Gustavo André dos Santos Lopes, David Soria Parra, Christian Stocker, Rob Richards, Pierre Joye, Zeev Suraski, Ilia Alshanetsky
-  * Status: ​Under Discussion, [[rfc:​releaseprocess:​vote|Voting ​is open]]+  * Status: ​Accepted, [[rfc:​releaseprocess:​vote|Voting ​results]]
  
 ===== Introduction ===== ===== Introduction =====
Line 55: Line 55:
 It is critical to understand the consequences of breaking BC, APIs or ABIs (only internals related). It should not be done for the sake of doing it. RFCs explaining the reasoning behind a breakage and the consequences along with test cases and patch(es) should help. It is critical to understand the consequences of breaking BC, APIs or ABIs (only internals related). It should not be done for the sake of doing it. RFCs explaining the reasoning behind a breakage and the consequences along with test cases and patch(es) should help.
  
-Se the following links for explanation about API and ABI:+See the following links for explanation about API and ABI:
   * http://​en.wikipedia.org/​wiki/​Application_programming_interface ​   * http://​en.wikipedia.org/​wiki/​Application_programming_interface ​
   * http://​en.wikipedia.org/​wiki/​Application_binary_interface   * http://​en.wikipedia.org/​wiki/​Application_binary_interface
Line 103: Line 103:
   * September, RC phases, biweekly release   * September, RC phases, biweekly release
     * each RC should go through the QA before being published     * each RC should go through the QA before being published
-      * usually2 ​days+      * usually 2 days
       * running the various test suites (phpt, custom real life tests, platform specific tests). Some tests need a day to run       * running the various test suites (phpt, custom real life tests, platform specific tests). Some tests need a day to run
   * November, Final   * November, Final
Line 133: Line 133:
   * Create a roadmap and planing according to this RFC   * Create a roadmap and planing according to this RFC
   * Package the releases (test and final releases)   * Package the releases (test and final releases)
-  * Decide which bug fixes can be apply to a release, ​inside ​the cases defined in this RFC+  * Decide which bug fixes can be applied ​to a release, ​within ​the cases defined in this RFC
  
 But they are not: But they are not:
rfc/releaseprocess.1308626831.txt.gz · Last modified: 2017/09/22 13:28 (external edit)