Thread

Just a point of clarification. The way I read things, it won’t be possible to have a new 1.x license past the end of the year; only 2.1 licenses will be available. Correct?

Yes, after December 31st, 2010 it will no longer be possible to acquire a new EE 1.x license.

We’ll be addressing import options for the Gallery and feature improvements post 2.1 which is why, like everyone else, we’re excited that the beta cycle is nearing an end. The Gallery import options will be free. And yes, we know this will be frustrating for certain types of EE sites and I apologize for that.

Thank you for this information Leslie. Not great news when you’re stuck with a number of galleries, but hopefully the longer wait before I can upgrade will mean a few more compatible 3rd-party add-ons. I’ll just have to cross my fingers and hope that my planned site changes will go smoothly on 1.* 😊

And thank you for letting download accounts apply towards 2.1 too. 😊 I imagine I will upgrade to take advantage of that even if I can’t actually use it until the Gallery import is released.

# We will continue to provide technical support for EE 1.x as long as there is sufficient demand for it. Realistically we expect this to be throughout 2010 and a good deal into 2011 at the least.
# EllisLab will provide six months notice prior to discontinuing EE 1.x support.

I think you are over optimistic about transition to EE 2.0 speed. It seems to me that for this transition to take place three, four or even five years should be expected.

EE 1.x has a large install base and those projects rely on many third-party add-ons, many of which are not converted. E.g. my project, although uncommon, relies on about 50 add-ons and only a couple of them are converted. I cannot simply stop the development work on the project and only do things related to conversion to EE2.0.

The same will be with other projects - they either are launched or are being developed and cannot be suspended simply because the transition to EE 2.0 must happen.

lets be honest - updating this EE site is no small task… and i do feel sorry for the people working on it! however, i sense this does mean that “near” means the EE version of “near” so August rather than July!

That aside - is the BETA version still getting build updates? so jumping in now would be a safeish move for commercial grade projects???

EDIT: Also is the CI site getting a facelift to bring it in line too??? 😊

The last build upgrade for EE2.02 was on April 30th 2010. The very next upgrade of any kind will be 2.1. A safe move if you don’t have mission critical add-ons that haven’t been changed to work with EE.

# We will continue to provide technical support for EE 1.x as long as there is sufficient demand for it. Realistically we expect this to be throughout 2010 and a good deal into 2011 at the least.
# EllisLab will provide six months notice prior to discontinuing EE 1.x support.

I think you are over optimistic about transition to EE 2.0 speed. It seems to me that for this transition to take place three, four or even five years should be expected.

Could be. We’ve done a major transition once before so we’re basing our rough estimates around that experience. It tends to go slowly and then quickly build up speed. I would not be surprised if we supported EE 1.x for 3 years, but 5 would be surprising.

That aside - is the BETA version still getting build updates? so jumping in now would be a safeish move for commercial grade projects???

There will be no updates between the current beta build and 2.1.

EDIT: Also is the CI site getting a facelift to bring it in line too??? 😊

We learned from past mistakes that updating more than one of our web properties at the same time is a bad idea.

We were fortunate to be involved in EE 2.0 early on and have enjoyed being part of the private and public beta testing teams. We feel there is at least an ounce or two of our feedback that’s been implemented in this new version and for the most part, we’re pretty happy with the product.

We’ve launched 3 websites in 2.0.x at this point and have about 35 in production (one project is a large MSM install and there are 7 single-site properties). We are working in 2.0.x every day now and our clients have been pretty understanding about the fact that EE is in Beta and that some features don’t yet work as expected.

For a while we were able to do frequent build updates for these clients and show progress and introduce them to *new* features as we kept their projects moving forward. Learning after a month without updates that there will not be another update until EE is out of Beta is understandable, and at the same time disappointing. I’ll be spending the week letting our clients know that we’ll be living with the bugs for the foreseeable future. It will be worth it in the long run through, as upgrading a live site from 1.6 to 2.0 will be avoided.

Right now most of the bugs we’re working with are things that annoy only the developer on the project, not our clients, and our newly launched sites are performing very well. It would have been nice to implement a build update now though, as we’re been living with many of these bugs daily for well over 2 months and EllisLab has spoiled us with EE 1.6.x in the last couple of years with all of its build updates. I’m just not use to living with EE bugs this long. 

Enough of my grumbling.

For those of you who are on the fence, jump into EE 2.0.x today. Start out with what you consider a basic site and give yourself some time to get your brain around the new possibilities and how they can fit into your business systems. It took me nearly a month to get use to the new interface and actually feel like I could think 3 moves ahead during development. Also, if you can, do some content publishing your self, so you get a better idea of what that experience is like in the new EE. We’re preparing a relaunch of our primary business site right now and having to republish a full site in EE 2.0 has really helped me anticipate my clients’ questions (our clients do their own publishing) and adjust our one-on-one publisher training sessions.

Really looking forward to the “soon” er… “near” launch of my new favorite CMS!

Fresh launched sites performing great in 2.0.x
http://www.dougy.org
http://simplycats.org
http://floral-dreams.com

Carthrob for 2.0 will be ready in plenty of time. Just FYI for the person thar asked.

I’d feel a lot better about all this if the fate of custom field support in SAEFs was known.  Not really excited about taking a huge step backward in that respect.

Also WTB extension hooks!

Not necessarily daily, but definitely useful since Ryan Irelan pointed it out in EE Insider: http://expressionengine.com/wiki/Config_Overrides/

For 2.x, this has actually been moved into the documentation proper, so no worries about losing it!

Edit: Er, wrong wiki page.  Nevermind, Lea!  The one I linked to is good too though. 😊

What will ultimatey happen to the 1.x codebase after EOL? I’m (granted, one of a very few) one who is less than impressed with 2.0 (e.g, Gallery removal) and I won’t be upgrading beyond the latest 1.x branch. Will the source still remain property of Ellis Labs?

Will the source still remain property of Ellis Labs?

Yes.

I love the news even that it has no date. It doesn matter if that takes 1 or 3 months, i’m happy to see that beta is soon out of “date”.  Why? hih, because of this:

The Discussion Forum module will see a significant update in the future, it is not slated for removal.  It is a lifeblood product that we use ourselves.  Work on the update will not begin until after ExpressionEngine 2.1 is released.  We will not communicate feature sets before we have a feature complete product in your hands, so you can evaluate if it meets your needs or not.  Engaging in discussion of what it will do and when doesn’t do anyone good; until you can try it, anything we say about capability doesn’t help you in a meaningful way.

I know that updates arent near but getting out from Beta is soooo good. Finally some really good news about the road EL is driving.

Cheers and thanks for the news, im pretty happy with this one 😊
- Pete

@FinPete
LOL…
“Work on the update will not begin until after ExpressionEngine 2.1…”

But this is great news mainly since it means that a lot of bugs have been worked out. If solspace updates their plugins then this is a good chunk of development tools that many sites simply can not function without loosing big features.
Either way a huge step forward.