[TYPO3-ect] TER clean up actions
Michael
typo3ml at schams.net
Sun Feb 19 11:00:39 CET 2012
On 19/02/12 20:08, Franz Holzinger wrote:
[...]
>> Because a lot of extensions do not have dependency settings yet the
>> script of the first cleanup can be used periodically to mark old
>> extensions as 'outdated'.
>
> not whole extensions should be marked as outdated but all old versions
> of these extensions.
I assume, Jigal meant *versions* of extensions.
"In the TER database all versions of an extension have their own
record." (quoting Jigal) Same in extensions.xml and in database table
"cache_extensions".
Should we use the terminology "extension record" in the future (which is
in fact a version of an extension)?
> Also all extension versions in experimental state should be marked as
> outdated.
Good point! What's about extensions in "test" and "obsolete" state? I
can't think about a situation where these extensions should come up in
the TER search or in the EM.
However, from a logical perspective, test and experimental extensions
are not "outdated" automatically (that would be a wrong definition). So,
I would not suggest that the intended script marks them as outdated, but
we could consider to exclude these states from the TER search and EM by
default, when someone is working on the changes anyway. What do you think?
The current list of valid states is: alpha, beta, stable, experimental,
test and obsolete.
Cheers
Michael
More information about the TYPO3-team-extension-coordination
mailing list