[TYPO3-core] Strategy for deprecation log
Jigal van Hemert
jigal.van.hemert at typo3.org
Wed Apr 3 13:09:23 CEST 2013
On 3-4-2013 12:38, Ernesto Baschny [cron IT] wrote:
> Jigal van Hemert schrieb am 02.04.2013 21:49:
>> On 2-4-2013 17:08, Steffen Müller wrote:
>>> very good. but what would be the default mode for new installations?
>>> production or development :)
>> A fresh install is of course in dev mode. But the visual sign should be
>> so obvious that no client accepts it when the site is launched.
> This is very developer-centric point of view. Why? I would say a fresh
> install is in production mode! Fast and without any nasty warnings,
> debug error messages, etc. It's clean and people can just "use it"!
It's more a practical point of view IMO:
Most of the TYPO3 installations are prepared by an integrator. After the
client has approved of the site the site content will be maintained by
the client (editor role). Only bugfixes and additional features will be
implemented by the integrator.
If someone is capable of installing TYPO3 and implementing a site with
it, he/she can also switch it to production mode once the site is launched.
If so desired we could have demo packages (introduction / government /
demo / whatever) that come with production mode enabled.
> If someone wants to debug some extension, is planning to upgrade, or has
> some trouble and needs more logging, he knows what he's doing (or will
> ask some developer friend or the community) and can then enable the
Then you are already in the situation where a complete site is running.
That should indeed be done in production mode.
I suggested to make the fact that development mode is active clearly
visible for all BE users. That way it's most likely that clients will
ask their agency / integrator about this and hopefully get them to
switch to production mode once the site is launched.
Jigal van Hemert
TYPO3 CMS Core Team member
TYPO3 .... inspiring people to share!
Get involved: typo3.org
More information about the TYPO3-team-core