Hacker News new | comments | show | ask | jobs | submit login

Exactly the same story here. Our primary product is stuck on Kohana 2.3.4 because of the lack of care that the Kohana team put into backwards compatibility. I wouldn't be surprised if they decide to essentially rewrite things again in the future either. If I could go back in time, I'd pick something else.

Kohana 2 was "just a php5 fork of CI", while Kohana 3 is practically a whole new framework. The "problem" is that Kohana team doesn't like handicaping new versions for sake of complete backward compatibility.

They just make the framework better with every new version, although in case of Ko3 minor versions are backward compatible (for example 3.0.8 with 3.0.1., but 3.1.0 will not be, at least concerning the response object and the ORM logics).

Yep. We are in exactly the same situation. Even moving to 2.4 looks to be a pain. The only brightside is that it's not THAT big of a framework, so patching it is not too bad. But still...

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact