pear:rfc:pear2_versioning_standard_revision

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
pear:rfc:pear2_versioning_standard_revision [2009/06/27 17:00]
cellog clarify pseudo-code, add examples
pear:rfc:pear2_versioning_standard_revision [2017/09/22 13:28] (current)
Line 7: Line 7:
   * Title: PEAR2 Versioning Standards Revision   * Title: PEAR2 Versioning Standards Revision
   * Version: ​  0.1.0   * Version: ​  0.1.0
-  * Status: ​   ​Incomplete+  * Status: ​   ​Draft
   * Type:      Standards   * Type:      Standards
-  * Last updated: ​June 27, 2009+  * Last updated: ​December 29, 2009
 ==== Author(s) Information ==== ==== Author(s) Information ====
  
   * Name:  Gregory Beaver   * Name:  Gregory Beaver
   * Email: cellog@php.net   * Email: cellog@php.net
 +  * Name:  Brett Bieber
 +  * Email: saltybeagle@php.net
  
 ==== Legal Information ==== ==== Legal Information ====
Line 73: Line 75:
  
 This document describes the versioning standards for the PEAR2 repository that will make the This document describes the versioning standards for the PEAR2 repository that will make the
-paranoia setting work.+paranoia setting work, and defines the version and api numbering process when backwards compatibility is broken. 
 + 
 +Breaking backwards compatibility requires changing the major '​A'​ in the A.P.I version. Once a package has been released as '​stable'​ the 
 +changing the major '​A'​ in the A.P.I version requires changing the major version '​X'​ in the X.Y.Z version in the package version.
  
 ===== Approach & Requirements ===== ===== Approach & Requirements =====
Line 157: Line 162:
 For the next release after version 0.1.0/0.1.0 (API/​Release):​ For the next release after version 0.1.0/0.1.0 (API/​Release):​
  
-still unstable: +   still unstable: 
-Breaking BC: API 0.2.0, Release 0.2.0 +   ​Breaking BC: API 0.2.0, Release 0.2.0 
-Adding major features: API 0.2.0, Release 0.2.0 +   ​Adding major features: API 0.2.0, Release 0.2.0 
-Adding minor features: API 0.2.0, Release 0.2.0 +   ​Adding minor features: API 0.2.0, Release 0.2.0 
-bugfix: API 0.1.0, Release 0.1.1 +   ​bugfix: API 0.1.0, Release 0.1.1 
-API bugfix: API 0.1.1, Release 0.1.1+   ​API bugfix: API 0.1.1, Release 0.1.1
  
-moving to beta: API 0.2.0, Release 0.2.0+   moving to beta: API 0.2.0, Release 0.2.0
  
-moving to release candidate: API 1.0.0, Release 1.0.0RC1 +   moving to release candidate: API 1.0.0, Release 1.0.0RC1 
-next release candidate: API 1.0.0, Release 1.0.0RC2+   ​next release candidate: API 1.0.0, Release 1.0.0RC2
  
-moving to stable: API 1.0.0, Release 1.0.0+   moving to stable: API 1.0.0, Release 1.0.0
  
  
 For the next release after version 1.0.0/1.0.0 (API/​Release):​ For the next release after version 1.0.0/1.0.0 (API/​Release):​
  
-moving to alpha: +   moving to alpha: 
-Breaking BC: API 2.0.0a1, Release 2.0.0a1 +   ​Breaking BC: API 2.0.0a1, Release 2.0.0a1 
-Adding major features: API 1.1.0a1, Release 2.0.0a1 +   ​Adding major features: API 1.1.0a1, Release 2.0.0a1 
-Adding minor features: API 1.1.0a1, Release 1.1.0a1 +   ​Adding minor features: API 1.1.0a1, Release 1.1.0a1 
-bugfix: <not applicable>​ +   ​bugfix: <not applicable>​ 
-API bugfix: <not applicable>​+   ​API bugfix: <not applicable>​
  
-moving to beta: +   moving to beta: 
-Breaking BC: API 2.0.0b1, Release 2.0.0b1 +   ​Breaking BC: API 2.0.0b1, Release 2.0.0b1 
-Adding major features: API 1.1.0b1, Release 2.0.0b1 +   ​Adding major features: API 1.1.0b1, Release 2.0.0b1 
-Adding minor features: API 1.1.0b1, Release 1.1.0b1 +   ​Adding minor features: API 1.1.0b1, Release 1.1.0b1 
-bugfix: <not applicable>​ +   ​bugfix: <not applicable>​ 
-API bugfix: <not applicable>​+   ​API bugfix: <not applicable>​
  
  
-moving to release candidate:​ +   moving to release candidate:​ 
-Breaking BC: API 2.0.0, Release 2.0.0RC1 +   ​Breaking BC: API 2.0.0, Release 2.0.0RC1 
-Adding major features: API 1.1.0, Release 2.0.0RC1 +   ​Adding major features: API 1.1.0, Release 2.0.0RC1 
-Adding minor features: API 1.1.0, Release 1.1.0RC1 +   ​Adding minor features: API 1.1.0, Release 1.1.0RC1 
-bugfix: <not applicable>​ +   ​bugfix: <not applicable>​ 
-API bugfix: <not applicable>​+   ​API bugfix: <not applicable>​
  
-moving to stable: +   moving to stable: 
-Breaking BC: API 2.0.0, Release 2.0.0 <This is *not* recommended ever> +   ​Breaking BC: API 2.0.0, Release 2.0.0 <This is *not* recommended ever> 
-Adding major features: API 1.1.0, Release 2.0.0 +   ​Adding major features: API 1.1.0, Release 2.0.0 
-Adding minor features: API 1.1.0, Release 1.1.0 +   ​Adding minor features: API 1.1.0, Release 1.1.0 
-bugfix: API 1.0.0, Release 1.0.1 +   ​bugfix: API 1.0.0, Release 1.0.1 
-API bugfix: API 1.0.1, Release 1.0.1+   ​API bugfix: API 1.0.1, Release 1.0.1
  
  
pear/rfc/pear2_versioning_standard_revision.1246122013.txt.gz · Last modified: 2017/09/22 13:28 (external edit)