Thread

One of the commercial licenses I bought for 1.6.x is used for my own freelance web development business.  I am intrigued by the new “Free Lancer” license and am anxious to see the feature set on Dec. 1st but anticipate it will meet the needs of my current usage.  So my question is “can I purchase the new free lance license for my site and transfer the old 1.6.8 license to another project (client project)?

Ho ho ho - it must be christmas eve if EE2 is out tomorrow!

Is everybody ready?

to quote Spongebob: “I’m ready! I’m ready! I’m ready!” 😉

to quote the famous Deuce Bigalow: “Cakes And Pies! Cakes And Pies!”

It’s 1st of December and I cant find any links to download EE 2.0.

Cheers

I am smelling the familiar chalky, yet sweet scent of Kool-Aid powder wafting through the air in this thread.

I understand some systems/products must go live to be fully tested. Server code typically must. But it all feels kinda skanky to me to charge for it in this way. Just be honest and let the community know the real reasons why: you’ve committed to a date and you aren’t really ready, and you can’t be confident you are without widespread live production testing. I’m okay with taking the risk of an unstable beta product; I’m not okay with paying for the risk too! I doubt many are either unless they are drinking the Kool-Aid.

Moreover, It is dubious to assert that this is a public beta. Betas, by definition, are not paid for. This is a paid beta and even worse you are paying them for you to find their bugs! I’ve never heard of such a thing and I’ve been part of dozens of betas, both receiving and delivering ends, since Photoshop 1.0. Public connotes free access, and access to all. Since you have to pay, it ain’t public. My 2¢ on redefining the word public.

I’d like to suggest a more equitable and attractive way: give free access to EE 2.0 beta to those who are already active registered users of 1.6.8. When the final product ships, for those people who wrote up one or more real bugs give them a free year subscription or maybe a 10% off for every real bug - this is in exchange for their risk-taking and time and trouble to write up the bugs. Have criteria for the bugs to keep like no dupes, no feature requests, the bug needs to be fixed in the final version to count, etc. Those that don’t write bugs aren’t really beta testing the product or weren’t affected by any lack of instability so nothing lost for them and nothing gained for Ellis Labs.

It’s 1st of December and I cant find any links to download EE 2.0.

Patience. Nobody said it was going to be released at midnight.

you’ve committed to a date and you aren’t really ready, and you can’t be confident you are without widespread live production testing.

We’ve been testing ExpressionEngine 2.0 in a Private Beta for 6 months with over 500 participants. A lot of bugs (and I mean a lot!) have been found that way. All of them? Certainly not: even with 1.6.8 we still catch the occasional bug, and try to fix it as quick as possible.

This is why we think it’s now time to open the Beta to the public in order to get it some “real world” use. We consider it ready for the rigors of the real world, even if there will be bugs and issues that are commonly associated with a Public Beta program.

Our support staff and dev team will work closely with users and provide a new build on a fairly regular basis. Just to be perfectly clear: this is living on the edge. If your project allows for such a scenario, we welcome your participation in the Public Beta. If you have a mission critical project on a tight release schedule, please use ExpressionEngine 1.6.8.

We think it’s the most responsible way to launch such a significant update. We did the same thing with ExpressionEngine 1.0 Beta, where the move from pMachine was at least as big a step for our users. Its part of our commitment to ExpressionEngine’s stability, security, and performance.

ExpressionEngine 2.1 will be considered the full release and be a free upgrade from ExpressionEngine 2.0 PB.

And lets be honest there are going to be few mission critical projects, high end sites that are going to be using EE2.0 without the major 3rd party plugins anyway.
Looking at some of Brandon Kelly’s predicted release dates for version 2.0 compatible versions of his plug-ins (Jan-July), who can really say they will be launching a site anyway.

I can foresee myself on 1.6.8 for at least another 4 months, even 6 months+.

Leslie,

Has a decision been made about the Core version of EE? Has the decision been made to scratch that version?

We have made the decision to discontinue Core for 2.0. There will be a way to evaluate the full version of 2.0 on your own hosting environment though. EE Core 1.6.8 will remain available.

Great decision, although i’m disappointed that the core version is being discontinued i think it’s a fantastic step forward for expression engine to be able to be demoed on your own hosting space, i hope this is free!! I know it seems silly but back when i first started looking at trying out EE, the $10 for a month just to demo an app just put me off.

And lets be honest there are going to be few mission critical projects, high end sites that are going to be using EE2.0 without the major 3rd party plugins anyway.
Looking at some of Brandon Kelly’s predicted release dates for version 2.0 compatible versions of his plug-ins (Jan-July), who can really say they will be launching a site anyway.

I can foresee myself on 1.6.8 for at least another 4 months, even 6 months+.

I see myself waiting 6+ months too. I know its against the EllisLab mantra, but I would like to know a time table for 2.1. I know dates can’t be put around releases, and I don’t expect there to be any, but I am interested in knowing what steps need to be taken for 2.1 to be assembled and released.

Also, will 2.1 have new features compared to 2.0, or will it simply be a bug free (as best as can be) version of 2.0?

I agree with nevsie. As much as I want to use 2.0 on the next project, there are just too many mission critical add-ons that won’t be released for months. Even if I could start a client site with 2.0, there have been too many occasions where the client has asked for a new feature, and usually an existing add-on gets it done. I’d be putting myself, and my team, in a tough position if we use 2.0 and such a feature is requested and the add-on I would have used hasn’t been ported to 2.0 yet. I don’t see myself using 2.0 until Spring of 2010, if not later, which sucks, because we’ve waited a year now just to have it released :/

And lets be honest there are going to be few mission critical projects, high end sites that are going to be using EE2.0 without the major 3rd party plugins anyway.

I know this shocks people but the vast majority of EE installs use zero add-ons and are 100% out of the box. That doesn’t hold for people who post regularly on this forum, but the active people on this forum represent only a small (but important) part of the community.

And lets be honest there are going to be few mission critical projects, high end sites that are going to be using EE2.0 without the major 3rd party plugins anyway.

I know this shocks people but the vast majority of EE installs use zero add-ons and are 100% out of the box. That doesn’t hold for people who post regularly on this forum, but the active people on this forum represent only a small (but important) part of the community.

I roll a couple 100% free of plug-ins. Simple and functional 😉

I roll a couple 100% free of plug-ins. Simple and functional 😉

We use just two third-party plugins/extensions, IIRC. And I have other sites that use none.

EE does a heck of a lot right out of the box.