I had the feeling that you reveal some interesting stuff here (the EnterpriseCM thing and the compat issues relating to PHP 4/5. I wish that the majority of the community could read that. If you think otherwise, no problem. It's your post, not mine

I am not sure I am revealing anything, Jason has posted
here and
there about the future of MODx and Tattoo (there are other threads, such as :
http://modxcms.com/forums/index.php/topic,4034.msg29423.html#msg29423or
http://modxcms.com/forums/index.php/topic,2135.msg41016.html#msg41016or
http://modxcms.com/forums/index.php/topic,6063.msg42909.html#msg42909or
http://modxcms.com/forums/index.php/topic,4076.msg29787.html#msg29787... there are certainly more...)
But you're right maybe we should have a summary of some kind somewhere.
Since I splitted and moved this thread to the english board, let me translate antoine's question on the french board was
I am a new member and I have often encountered references to Tattoo, is it the new name for MODx 1.0 ? How does it differ exactly ? Is the brand changing or is the project forking into two different branches ?
My answer was :
I understand how you could be confused about this... First, to have a good grasp of how things are going on as far as dev is concerned, you'll have to keep in mind that there are two main branches :
- the 0.9.x branch, which I could call the Eto legacy branch, with many improvements over Etomite
- the 1.0 branch, which is a total rewrite of the core, based on OO
This being said, the 1.0 branch splits into two different versions of the application (so to speak, forgive me if I am making improper use of language here, I am no dev

) :
- MODx 1.0 will remain compatible with PHP 4.x, and will probably target individual or small companies (due to the price / scarcity of PHP5 hosting)
- Tattoo, which will be a "PHP5 enhanced" version of the above (will require PHP 5.1+), targeted at corporate websites and possibly the ECM segment.
The new branch will bring a lot of improvement to the existing features :
- database abstraction layer, which will open the use of DB other than MySQL
- a new much more powerful API
- a new permission system
- revisionning
- mutli-lingual capability
- workflow
- and many other....
I'll let the dev team correct me where I am wrong or not precise enough there.