[Typo3-dev] database normalisation

[dan frost]

I realise all this - and i think the only way to decide if it's possible 
and sensible is to try it. So, we don't "branch" properly. We just take 
a copy of TYPO3 now and muck around with it...

The alternative is months and months or discussion with no solid proof

dan

> As we know it'll break compatibility. So Kasper will not accept the 
> changes or it'll need strong arguments ("it's cleaner" is not good enough).
> 
> You might end up with some kind of "alternative releases". Is the cause 
> a good reason for such releases? TYPO3 has now many extensions and 
> having (slightly) different "branches" will weaken TYPO3.
> 
> Masi