Would it better to instead use a non-volatile name like ConcreteCMS or ConcreteMVC or ConcreteFramework?
(Sorry if this seems nit picky! I should also mention I am extremely impressed with this project, and have recommended some of my colleagues try it out.)
there will never be v6. we’re gonna get it perfect with this one..
10 Mar 09 at 11:01 pm
Thanks for clarifying.
So the core is intended to remain static, but the add-ons will be changing and be upgraded for years?
Also, how long do you expect Concrete5-core will be used, more than 10 years from now?
1) the core should be small and stable. not every idea is a good idea, and a lot of good ideas just don't play well together. As we continue to grow you can expect the frequency of core changes to slow down. (right now we release a new version every couple months)
2) if we do pass 5.9 in the next couple of years, there's no reason 5.10, 5.11, 5.12 etc wouldn't work.
3) no, the branding wont be changing. it was actually called Concrete CMS years ago, and that's a hard name to protect and no one outside of developers knows what a CMS is.
(I was wondering about this, too.)