rfc:peclversioning:solution2

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
rfc:peclversioning:solution2 [2008/04/02 16:00] pajoyerfc:peclversioning:solution2 [2017/09/22 13:28] (current) – external edit 127.0.0.1
Line 50: Line 50:
     * A version string **must** include a major, a minor and a patch level number (x.y.z) Please note that all are version numbers are mandatory.     * A version string **must** include a major, a minor and a patch level number (x.y.z) Please note that all are version numbers are mandatory.
     * A package version has a "state" (as indicated in the package.xml file), which describes the maturity. The state may be one of "alpha", "beta", "RC" or "stable" (listed in the order of code maturity). Please note that the state "RC" is achieved by using the state "beta" and appending the version number with "RC" followed by an integer     * A package version has a "state" (as indicated in the package.xml file), which describes the maturity. The state may be one of "alpha", "beta", "RC" or "stable" (listed in the order of code maturity). Please note that the state "RC" is achieved by using the state "beta" and appending the version number with "RC" followed by an integer
-    * The state should always be added as a suffix unless the state is "stable" 'a', 'b' or 'RC' (respectively for alpha, beta and release candidate) followed by a numeric value. E.g. '1.2.1b3', '1.0.0RC2', '1.1.0a1'+    * The state should always be added as a suffix unless the state is "stable".  Valid suffixes are 'a', 'b' or 'RC' (respectively for alpha, beta and release candidate) followed by a numeric value. E.g. '1.2.1b3', '1.0.0RC2', '1.1.0a1'
         * //Note that the PEAR installer cannot recognize hyphens in a package version string//         * //Note that the PEAR installer cannot recognize hyphens in a package version string//
     * In package.xml, the 'status' field for a release may be any of "alpha", "beta" or "stable". These states should be reflected in the version number: a "stable" release should be at least 1.0.0, for example. A Release Candidate is signified by RCx in the version number and a "beta" status in package.xml.     * In package.xml, the 'status' field for a release may be any of "alpha", "beta" or "stable". These states should be reflected in the version number: a "stable" release should be at least 1.0.0, for example. A Release Candidate is signified by RCx in the version number and a "beta" status in package.xml.
rfc/peclversioning/solution2.1207152032.txt.gz · Last modified: 2017/09/22 13:28 (external edit)