Thread

I’d like to know when CI 3 is expected to be released.
Does anyone know?

Thanks

There is no release date set yet.
There are still some issues to fix. (https://github.com/EllisLab/CodeIgniter/issues?milestone=2&page=1&state=open)
Anyway - cross your fingers… maybe at the end of the year.

Thanks a lot. I frequently view this page.
I’d like to know if there is a roadmap more detailed.

So, I don’t want annoy anyone with this question: I love CI and I’m only curious to know details.

It bothers me see Symfony 2, Zend Framework 2 😊

Hi all,

I guess the only and the most important question is when CI 3 will be released. the only chance to get CI to it’s natural place is by releasing to 3.0 version.

So anyone has an answer when it’s gonna be.

I would say just use the current repo from the Github page.The 3.0 branch is stable enough to use for production.

I would say just use the current repo from the Github page.The 3.0 branch is stable enough to use for production.

Thanks, but one extra stupid question how to get the documenation for this version version. I see it’s on python. how to do it. Thanks in advance

Thanks, but one extra stupid question how to get the documenation for this version version. I see it’s on python. how to do it. Thanks in advance

You have to install Sphinx and Python in order to build the user guide locally. Pretty simple on linux, but I wrote an article about setting up the user guide on windows. I am on windows, so I wrote a little batch script that runs the sphinx command line with arguments to build it easier. Once you have set it up, it’s really easy to create.

Hi

Is this new version stable ?

And can I update 2 to 3 ? I’m currently making an ecommerce…

Hi

Is this new version stable ?

And can I update 2 to 3 ? I’m currently making an ecommerce…

I would version 3.0dev over 2 for a new project. Although not official, there have been a number of bugfixes after the 2.1.3 release.

It needs a new owner before it gets released without doubt..

See other threads and news annoucement

Here, I am feeling frustration about no release news yet on CI 3, from long long time we are waiting for CI 3 release but we need to wait more :(

I want to suggest one big change…
CI 3.0 to become CI 2.2.
Drop all ToDo’s which can’t be finished fast and make it Public..

For CI 3.0 there should be made some major changes.
PHP stop support for 5.3.* versions and CI 3 (which is not even ready) is pointing at 5.2.4..
There is no point.

If Ellislab want to not support it any more OK. But at least complete your started tasks..

Here, I am feeling frustration about no release news yet on CI 3, from long long time we are waiting for CI 3 release but we need to wait more :(

It isn’t that different than CI 2 (as of right now). With someone new taking over CodeIgniter, it should be completely rewritten using modern PHP standards.

Hi

Where is the guide to update CI 2 to 3 ? I think that I saw it on Github but I can’t found it…

Thanks.

I want to suggest one big change…
CI 3.0 to become CI 2.2.
Drop all ToDo’s which can’t be finished fast and make it Public..

For CI 3.0 there should be made some major changes.
PHP stop support for 5.3.* versions and CI 3 (which is not even ready) is pointing at 5.2.4..
There is no point.

If Ellislab want to not support it any more OK. But at least complete your started tasks..

I disagree CI 3.0 to become CI 2.2. The major version should be incremented, because there is a new, strong “ucfirst” naming convention. There is also a new API-convention “Return NULL, (not FALSE anymore) if you have nothing to return”. There are some new features within the database query builder (thank you, narfbg). There is an “official” native PHP-session driver.

There is important history (issues, messages, pull requests) in github, where everybody refers to CI 3.0.

I have already released in public two libraries, that are able to work with CI 2.x and CI 3.0-dev, and inside them I am checking the CI major version in order to deal with some extensions of the API. It is easy these checks to be corrected, but I don’t want confusion for somebody else.