[TYPO3-ect] Ideas to clean up TER

Jigal van Hemert jigal at xs4all.nl
Sun Jan 29 07:26:53 CET 2012


Hi,

 From a small Twitter conversation with Xavier Perseguers and Helmut 
Hummel the idea was born to clean up TER a bit and remove *) old extensions.
Of course the registration and status will not be removed to make sure 
they show up as the Extension Manager as removed/unsupported.

Proposals:

1. the version constraints in em_conf.php will become mandatory (and 
cannot be higher than the current development version (a.k.a. "master"))

2. once a TYPO3 core version becomes end of life the extensions which 
have that version as the upper limit will be removed from TER

3. there will be a grace period for extension authors to update their 
extensions. Extension authors will be notified (on the address 
registered in typo3.org) of this change. This change will be published 
in the relevant places (newsgroups/mailing lists, typo3.org)

4. the procedure to transfer extensions will be slightly adapted for 
extensions which were removed because of "old age".


Questions:

- do we need a new 'status' to reflect the fact that an extension is 
removed because it's considered old (instead of insecure)?
- should authors be notified before a core version becomes EOL that 
their extension will be removed?

What do you think?


*) Removed as in: not available for download in TER.

-- 
Kind regards / met vriendelijke groet,

Jigal van Hemert.


More information about the TYPO3-team-extension-coordination mailing list