Feature #82008
closed
TER / ExtensionManager should provide a new attributes to simplify TYPO3 Extension-Updates
0%
Description
TER / ExtensionManager should provide a new attributes:
Flag: "versionPurpose"
declaring the purpose of the current extension-version with tags like
"security-fix" or "new-feature".
Flag "updateType":
declaring if the version needs special attention while updating. It could contain tags like:
"unattended", "attended", "needs-manual-processing" to inform TYPO3-Admins (or unattended update-scripts") how to process with an update.
Of course these flags always can declare this from a previous to current (TER) version. So for updates from much more previous versions one (the admin or an extension doing this in future) needs to be setup either not doing such updates or check all previous versions from the current one to get an overview from version n.n.n to ter-version n.n.n about update processing (f.e. shown as collapseable table in such an extension).
Currently updating TYPO3-Extensions always is a risk as one cannot see if there is any potential technical risk that the extension/plugin may not work correctly on demand afterwards.
Updated by Georg Ringer over 7 years ago
- Status changed from New to Rejected
Thanks for creating this issue, however there is already such thing which is called semver, read about it at http://semver.org/ which means (copied from their website)
----
Given a version number MAJOR.MINOR.PATCH, increment the:
MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards-compatible manner, and
PATCH version when you make backwards-compatible bug fixes.
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.
---
additionally the Security Team flags insecure extensions.
However yes, the core and extension authors must follow more this principle which is used every where else.