rfc:peclversioning

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
rfc:peclversioning [2008/04/02 15:17] – old revision restored pajoyerfc:peclversioning [2008/04/02 15:22] pajoye
Line 53: Line 53:
         * //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.
 +
 +The following points can be added to extend this RFC to fit some basic needs requested by our users or 3rd party. The main goal is to define when a package can break the backward compatibility, add features. There is no technical restrictions or requirements, these points only define how to choose a version number according to the changes done in the release.
 +
 +//Please note that these points are subject to discussions as some developers may not like to be forced to use a given version number. Please mention your preference in your vote or feedbacks/comments //
 +
     * A backwards-compatability break may include feature additions     * A backwards-compatability break may include feature additions
     * A feature addition may include bug fixes     * A feature addition may include bug fixes
rfc/peclversioning.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1