[TYPO3-ect] Ideas to clean up TER

[Michael]

On 29/01/12 21:27, Xavier Perseguers wrote:

[...]
> We have Forge SVN/git for accessing old versions or old extensions.

I am not convinced, that a *version control system* such as SVN or git
is the right solution for an archive requirement, to be honest.

Also: how many of the 5500 extensions currently available in TER are
committed to SVN? Would you plan to sort out which are not in SVN yet
(and declared as "unmaintained") and submit them, so that we have them
archived?

>> It would be a "nice-to-have" feature to inform extension developers in
>> two stages:
>>
>> (1) when a new stable TYPO3 version has been released that is *not*
>> listed in the em_conf.php array [...]
> 
> I'd say NO! There are already enough way of being advertised that a new
> version of TYPO3 is out [...]

Well, I don't mean "advertising" of every new TYPO3 version, I mean a
notification if I (as an extension developer) should *do* something (or
at least consider doing something) to keep my extension up-to-date. So,
I would be notified if a specific TYPO3 version has been released that
my extension currently does not support (is likely not tested with).

But I am not too stressed about the first stage and maybe you are right
and this is not necessary. What do the others think?

Cheers
Michael