Thanks Leslie, for your post and for answering questions in this thread.
I want to voice some concern about EE 1.x being no longer available for purchase as of 1/1/11:
First, let me say that we appreciate having months of warning, and now are shooting to transition to EE 2 before December this year. That’s an OK enough target, at this point.
My concern is, however, that we’re in a pickle if we can’t make that target.
What this transition, from EE 1.x to 2.x, is asking of us is that we budget additional time for R & D (making our processes work with EE 2.x) vs production (building sites in EE 1.x). Our time is already pretty booked-up into the Fall. And, we have a lot of things our clients like us to do for them, that we know exactly how to do in EE 1.x, that are going to take an unknown amount of time to work out in EE 2.x.
While your post signals to us that we need to go forward with working out those things in EE 2, we really don’t know if we can make that transition 100% before the new year. For example, if it’s going to take us 120 work hours, we don’t know if we’re going to be able to actually budget 120 work hours between now and then.
So, I hope that concern is clear, and that you will keep open the possibility of extending EE 1.x availability into 2011. I hope that we ourselves don’t need EE 1.x next year—and I hope that EE 2.x plus add-ons can do what we need. But, I am concerned enough to ask for the extended availability for EE 1.x into 2011.
Finally, let me note that, from our perspective, the EE 2 beta has not been something we could work with in a way that allowed us to start this transition. So, we’ve been waiting for the release of the non-beta 2.1, to start a serious transition process. From the non-beta release date, we would ask for at least 6 months of continued availability of EE 1.x.