[TYPO3-typo3org] typo3 4.0.5
9f4eetb02 at sneakemail.com
Fri Mar 9 10:41:39 CET 2007
Ernesto Baschny [cron IT] wrote:
> Dmitry Dulepov wrote: on 08.03.2007 13:17:
>>> Some of my extensions used mmforeign in the past. In 4.1 the MM
>>> support of
>>> the core has been improved. Before I update to 4.1 I need to test how it
>>> will work together now. Can remove mmforeign? Do I have to keep
>>> Will I get conflicts between mmforeign and the new MM support of the
>>> Will I have to modify my extensions?
>>> So for some customers I will work with 4.0.x until all testing is done
>> I agree with your case. But your example does not correspond to original
>> problem :) Original problem was that upgrade from 4.0.4 to 4.1 is more
>> complex than from 4.0.5, which (I believe) is not really so.
> The original problem is that 4.0.5 is not offered for download on
> typo3.org anymore. So people that have 4.0.1, .2, .3 and .4 and want to
> upgrade for the sake of security (not features), will have to search on
> sourceforge or other places.
Well, this is normal. Why offer previous version if new is available?
Core team is interested to support less vesions, so it is natural that
only 4.1 is proposed on the main page.
> So I also suggest that on:
> we have the latest 4.1 (stable) release, but also the latest security
> update from the previous (stable) release, which would be 4.0.5.
+ words that anyone is encouraged to update/install 4.1.
"It is our choices, that show what we truly are,
far more than our abilities." (A.P.W.B.D.)
More information about the TYPO3-team-typo3org