Feature #37150
closed
Force TYPO3 dependency setting on TER upload
0%
Description
Following a proposal by Xavier Perseguers, Helmut Hummel and Jigal van Hemert in early 2012 to make the TYPO3 dependency mandatory for all extensions in order to identify outdated/unmaintained extensions, the Extension Manager should force the user to set the TYPO3 dependency when uploading an extension to TER.
See "TER Cleanup" initiative at:
http://lists.typo3.org/pipermail/typo3-team-extension-coordination/2012-February/003955.html
(quote) New versions of extensions need to have a dependency on TYPO3 for at least the lowest currently supported branch. When uploading an extension this dependency must be checked and missing or too low dependencies must be rejected
In order to encourage users to provide the information about the TYPO3 dependency, the EM should allow (force?) the user to state the min and max TYPO3 version, e.g. "4.0.0 to 6.0.999" (if this information does not exist in "ext_emconf").
Updated by Oliver Hader over 11 years ago
- Project changed from 2269 to TYPO3 Core
Updated by Ernesto Baschny about 11 years ago
- Status changed from New to Needs Feedback
- Priority changed from Should have to Won't have this time
Is this really required? Doesn't TER already enforces this? Since we have so many ways of "uploading an extension" now (old EM, old new EM, ZIP upload in TER, CLI tools etc) it would be easier to have this check implemented only in the TER component.
If you agree, we should close this issue (also considering that the 6.x EM doesn't even provide an interface to upload extensions to TER...).
What do you think?
Updated by Michael Schams about 11 years ago
Is this really required? Doesn't TER already enforces this?
Not yet, but hopefully in the next few weeks, as soon as the new version of EXT:ter is installed at T3O.
http://typo3.org/news/article/ter-new-requirement-for-extension-upload/
...would be easier to have this check implemented only in the TER component.
Personally, I would argue, that a tool (does not matter, if it is the old EM, TER-FE, a CLI tool or whatever) should not try to upload an extension to TER, if it is clear that this attempt will fail (e.g. because of a missing TYPO3 dependency). An upload attempt is pointless and the tool should catch this error. Why trying, if we already know that TER will reject the upload in 100% of all attempts?
On the other hand, given the fact that I reported this ticket over a year ago, and you are absolutely right, the Extension Manager does not provide an upload-to-TER functionality any more, I agree, we can close this issue.
New tickets can be opened for components which upload extensions to TER, if required.
Updated by Alexander Opitz almost 11 years ago
- Status changed from Needs Feedback to Closed