Thread

That’s like saying McDonalds should serve Burger King hamburgers. Won’t happen.

:lol:

Actually, we are ensuring that CodeIgniter has a solid future. The process of looking for a new owner and handling the transfer is taking far longer than we anticipated, but there are a lot of considerations and moving parts to ensure its success.

Sounds really perfect! Derek is there any tentative release date available for 3.0? Can you confirm if you actually found a new owner or if you are still looking for it? I am not asking what is the company name, just curious where we are after these few years…

Thanks

Reasonable questions, NiconPhantom, but we really can’t talk about it until we are able to publicly talk about it. 😊 Stay tuned to the blog, we certainly aren’t going to artificially delay conveying information to the CodeIgniter community as soon as we are able to.

Thanks Derek!

The question was,, Estimated/expected CI 3.0 Release date.

Thank you!

It will be good to release that CI 3.0 Final….
So many people are working with CI and such endless development is NOT NICE!
Its better with fix versions than with that stuck on not Final version..

This endless development is like a joke with all developers who likes CI..

IMO there should be Release Candidate / RCx builds of V3.0. The continual round of changes is a bit off-putting even when they are very minor.

You want a release before the release ... that’s not how it works. RC tags (not builds, nothing is compiled here) only make sense for the final thing - it’s a feature freeze point and what you see is what you get, except bug fixes. There is one major feature left to be completed: Sessions.

Want a release before the release? Download it off Github and use it now. I am, it’s stable and works great. Just don’t expect support since it’s not official yet.

The only gotcha is if you overload core methods/libraries you need to watch any subsequent commits to see if they impact your changes.

There is one major feature left to be completed: Sessions.

Hi Narf, could you explain a bit more? What’s the problem with Sessions?

There is one major feature left to be completed: Sessions.

Hi Narf, could you explain a bit more? What’s the problem with Sessions?

https://github.com/EllisLab/CodeIgniter/issues/2476
https://github.com/EllisLab/CodeIgniter/pull/1780
https://github.com/EllisLab/CodeIgniter/issues/2702
https://github.com/EllisLab/CodeIgniter/issues/1344

Also:

- They don’t implement locking - unsafe for concurrency.
- The default (and only one available, until 3.0) storage is cookies, which means both storage and authentication is client-side, unless you use a database, and even then there are issues.
- The code is practically unmaintanable.

It’s all the result of an old application design, that was made to work around the issues of the past and sparingly patched by random contributors. I’d elaborate more, but it wouldn’t make a difference because the bottom line is - it’s broken, it needs to be replaced and few people understand all of it to do that properly.

Just to be clear - this doesn’t mean to rewrite your applications not to use the existing sessions in CI. If they have worked for you until now, then that’s just fine and you’ll get the improvements later with the 3.0 upgrade (the replacement will be backwards-compatible). It just means that there are some problems and they need to be addressed.

Any news in release date CI 3.0? Or in new owner of CI?

Recently I saw this article http://phpsblog.agustinvillalba.com/hmvc-modular-applications-codeigniter/, posted on April 12, 2014. Well, it is about CodeIgniter 2, the “comfortable” good old one.

Make for yourselves an experiment: Try to find good articles about CodeIgniter 3. You will find nothing. Bloggers will not write about unreleased CodeIgniter. And after v.3 release time would be needed for accumulation of good fresh articles, tips, examples, tutorials. Third-party libraries would need time for adaptation too.

I think, holding CodeIgniter 3 release anymore is very counterproductive, no one has interest in this situation.

Please, fellow developers, don’t rush for proposing new features right now. Let this release go.

...
Please, fellow developers, don’t rush for proposing new features right now. Let this release go.

Or rather, don’t be disappointed that 3.0 won’t have what you propose.
Feature proposals are not blocking the release, don’t worry about that.

On this page: https://github.com/EllisLab/CodeIgniter/issues/milestones

We can see:  v3.0.x -> 100%

So, why it isn’t released ?