Dean post a few complaint about why I made an exception for MODx so I have to remove MODx from the site for now.
-
MODX Staff
- 12,272 Posts
I’ll summarize what I put in the email, and make a conclusion that I’ve been wanting to do anyway: TP3.3 = MODx 1.0 It certainly is robust, stable and capable. If we have to call it that in order to pacify whiners, the let’s do it!
It’ll be out tonight or tomorrow. Just need a tiny bit more testing, but from what I can tell, it’s really solid.
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
I’d wait till we get TP4 going and then rebrand it as Tattoo before we do anything else. Or, if the need be, we could always just rebrand TP3.3 and release it as an official 1.0 once we work out the bugs and stuff. Then, once we get TP4 done, we could release it as a 1.1 release. Just a thought.
Jeff Whitfield
"I like my coffee hot and strong, like I like my women, hot and strong... with a spoon in them."
Adam,
It is not the number that make it a release! It is how you decide to call your release.
Some people will call 0.6 release and then 0.6.1 beta, rc1, rc2 then 0.6.1 release
That is how most CMS package number their alpha, beta, rc and release.
-
MODX Staff
- 12,272 Posts
Hrmmm... since MODx is not exactly where we want it 150%, why not just call it MODx .9... and in a few months: Tattoo 1.0. Building a support site all over again in a flash is not exactly what I’m looking forward to at the moment.
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
-
☆ A M B ☆
- 24,524 Posts
I like our support site. :’(