rfc:clear-process
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
rfc:clear-process [2019/04/25 09:41] – krakjoe | rfc:clear-process [2019/04/25 09:42] (current) – krakjoe | ||
---|---|---|---|
Line 10: | Line 10: | ||
This RFC seeks to clarify the process of introduction, | This RFC seeks to clarify the process of introduction, | ||
- | ===== Introduction ===== | + | ===== Introduction |
The introduction of new code that retains ABI compatibility may occur in minor versions. Should the new code fail to maintain ABI compatibility, | The introduction of new code that retains ABI compatibility may occur in minor versions. Should the new code fail to maintain ABI compatibility, | ||
- | ===== Modification ===== | + | ===== Modification |
The modification of existing code that results in no backward compatibility break, and retains ABI compatibility may occur in a patch version: This covers the vast majority of bug fixes, for which we require no RFC. | The modification of existing code that results in no backward compatibility break, and retains ABI compatibility may occur in a patch version: This covers the vast majority of bug fixes, for which we require no RFC. | ||
Line 20: | Line 20: | ||
The modification of existing code that results in a backward or ABI compatibility break must not occur in a patch version: For this minority of bug fixes and minor enhancements, | The modification of existing code that results in a backward or ABI compatibility break must not occur in a patch version: For this minority of bug fixes and minor enhancements, | ||
- | ===== Deprecation ===== | + | ===== Deprecation |
The deprecation of existing code must occur in minor versions. Deprecated code shall be assumed to be targeted for removal in the following major version. | The deprecation of existing code must occur in minor versions. Deprecated code shall be assumed to be targeted for removal in the following major version. | ||
Line 26: | Line 26: | ||
Should the focus of an RFC be on deprecation, | Should the focus of an RFC be on deprecation, | ||
- | ===== Removal ===== | + | ===== Removal |
Removal must only occur in major versions, no code shall be removed before being deprecated. | Removal must only occur in major versions, no code shall be removed before being deprecated. | ||
Line 32: | Line 32: | ||
Should the focus of an RFC be on removal, and should that RFC be accepted, deprecation shall be carried out as described above. | Should the focus of an RFC be on removal, and should that RFC be accepted, deprecation shall be carried out as described above. | ||
- | ===== Voting | + | ==== Voting ==== |
Should this RFC be accepted, a new section in the voting RFC shall be created containing the information agreed upon here. | Should this RFC be accepted, a new section in the voting RFC shall be created containing the information agreed upon here. | ||
- | ===== External References | + | ==== External References ==== |
http:// | http:// | ||
rfc/clear-process.txt · Last modified: 2019/04/25 09:42 by krakjoe