Thread

sorry - a little confused by that last post(edit-the one before last)! But yes happy building on Version 1. And have launched projects since the first mention of EE2 so no problem there.
I was simply saying that there was an event mentioned to the EE community, it has passed, and it went quietly - i was surprised since the quote i added in the above.

I am not placing expectation, i am not trying to throttle them for feature lists, release dates, etc, etc, etc.
I am simply asking if everything is going well.
In the same vein - i followed reports of Windows7 (i feel ashamed!), i followed project details on FF3.5, my mobile phone contract is up from renewal in a few weeks - i started reading up on new phones due out. All with general interest.

I guess i am just a little disappointed that i am now honestly worried about asking, mentioning, whispering the letters EE2.0 on the forums without people whinging/flaming! In tribute to harry potter I guess it is “Software that must not be named”!!!

Things are going very well thanks nevsie. Reports are coming in, getting addressed, and making EE2 better.

thanks, glad to hear it is going well and testers are active.

thanks, glad to hear it is going well and testers are active.

We’ll still be doing 2.0 updates every two weeks on the EE Blog, so we’ll keep everyone in the loop as much as possible.

The short answer to your question is that Jones is very serious about EllisLab taking an old fashion approach to beta testing. This means that Beta1 is full of bugs and rough edges. The purpose of the beta is not marketing or hype, but finding a small group of testers willing to put in the time to discover bugs, and provide feedback which we’ll use to smooth out the rough parts.

Do we have any idea on what pricing will be? I’m still using it for personal blogging and am curious as to whether I’ll be able to afford to move up.

Hi Les!

Long time no see on the forums, but you are definitely remembered and welcome anytime.

We’re actively working on the pricing now, but no final decisions have been made yet. However, we’re not considering anything to drastic in terms of pricing (like uber price jumps, weird limits on users, or tighter license restrictions). We’re using the opportunity to revisit just about every policy we have with an eye for making it more friendly, understandable, and usable to developers and the community.

Inbetween while waiting for 2.0 I have played around with some other CMS; nowhere there is such a good support as at EE. So for me a higher price would be definitely ok, on the one hand for the good product, (even more) on the other for the excellent support, which until now solved all of my problems in a friendly and competent matter.

i look forward to these updates every two weeks. the anticipation is killing me. i have been geeked about 2.0 since this time last summer.

I am very much looking forward to the new version, but I’m not in a hurry.
I’ve started getting my head around PHP and will be learning CodeIgniter to be the first PHP Framework I’ll ever have worked with. It can only come in handy when the new EE version comes out. So, thank you for keeping us in the loop. (and keeping us in suspension at all times)

It would be great if someone could put a new blog post on the Code Igniter site about the BETA testing and how it relates to Code Igniter.

The last blog post was about 1.7.1 and that was back in February of this year! We don’t expect miracles and we know things take time, but not hearing anything on the CI front is not good for the community.

It would be great if someone could put a new blog post on the Code Igniter site about the BETA testing and how it relates to Code Igniter.

The last blog post was about 1.7.1 and that was back in February of this year! We don’t expect miracles and we know things take time, but not hearing anything on the CI front is not good for the community.

I’ve spoken about this a bunch of times. Here are two reasonably recent postings; its not all, its just what I could find off hand (one, two).

Since its a direct answer to your question, here’s what I wrote that I think most immediately and directly answers your question:

Thanks everyone. Everything I would want to say has already been said (much better then I could say it) so just let me do a quick “official” wrap up (I’m not closing this thread or anything, just want to summarize/add a few things).

EE 2.0 is what was announced, not CI 2.0. If EE needs something, then CI gets it, but as it stands right now, EE2.0 is actually out in people’s hands, being used, being coded for. A more broad public release is coming, but it is not vapourware - although yes, it took longer then we anticipated for all types of reasons.

EE 2.0 runs on a nearly stock install of CI from the SVN. What is not in there is the aforementioned javascript library, which frankly most people here (CI devs) would neither want or need. CI continues to be under active development, check the SVN and you’ll still see stuff happening. We aren’t hiding anything from you.

I’m sorry if I created any artificial expectations for anyone about CI 2.0 - not my intention. CI continues to be a flexible, fast, intuitive framework that derives most of its value from the intelligence of the coder using it, and the community around it. The next version of CI will not change this.

Beta testing for CodeIgniter can happen from the subversion repository, where you can access up to the second code in CI - this also generally serves as our beta version.

I hope this is helpful. Your point about increased communication with CI is not lost on us though, and I’ll make efforts to communicate any changes as they come up.

Derek,
I hope you all plan on including the js library in a future CI release. I have actually been looking forward to this.

What is not in there is the aforementioned javascript library, which frankly most people here (CI devs) would neither want or need.

I hope that is just in reference to the current SVN releases…

You bet, our plans have not changed, we intend the js lib to be included.

Oh joy! <sigh of relief>

I am also giddy, as it is “Update Tuesday”! Woo Hoo!

No updates today?

No updates today?

Sorry guys, we had a couple health issues (colds) come up and when that happens covering takes precedent over the blog update. I’ll get one up tomorrow.