This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
February 27, 2010 10:16am
Subscribe [0]#1 / Feb 27, 2010 10:16am
is there a roadmap for the development of EE2?
We are at the start of a project that is going to take about 6 months to develop, and I would like to know if it’s worth starting with the Beta.
I would only do this if the ‘real’ product is ready by the time of launch.
Obviously you cannot look into the feature, but I’m sure you must have some kind of ETA?
thanks
#2 / Mar 01, 2010 12:18pm
Hi, Nilz - please see is there an ExpressionEngine roadmap?
We do not have an ETA for 2.1. But remember, EE 2.0 non-commercial and commercial both include 1.x, and there is a clean upgrade path, so you can start with our stable product and upgrade from there as needed.
#3 / Mar 01, 2010 1:52pm
Thanks Lisa
I know about the upgrade, but I’m really keen on giving the user a nice interface to work with including the nice file manager, and image editor that is missing from version 1.
Personally I don’t mind using a beta product, since it seems really stable, but the client might find it a bit weird to pay for a beta product.
Isn’t it very customary to have a roadmap, or deadline for a piece of software to work towards? Why has Ellis chosen not to do this?
Niels
#4 / Mar 01, 2010 1:58pm
Hi, Nilz - the reason behind our decision is explained at the link I provided. To quote:
Roadmaps are unreliable. If we say Feature X will be available on Date Y and then it isn’t, people get mad. This gets compounded if people are making business decisions based on a roadmap. And people will make business decisions even if we have big disclaimers in bold red type based on a roadmap. The reason for the delay usually doesn’t matter to people either.
We don’t like people making decisions on features that aren’t released. Further, until you can actually experience a feature you won’t know if it will really work for you. So even if the feature is released on the projected date you’d still have no way to evaluate if the feature meets whatever needs you might have. In our opinion the whole thing just gets messy and leads to PR nightmares that can simply be avoided with one little line:
Always, without exception, make decisions regarding EE based on what’s currently available.