Topic: v1.0-dev using CodeIgniter 2.0 |
|||
|---|---|---|---|
Posted: 2010-05-12 |
|||
Admin
|
As soon as the source code for CodeIgniter 2.0-dev was released I converted PyroCMS to run on it, but it was a little buggy back then. Seeing as CodeIgniter 2.0 is now considerably more stable it makes sense to move the v1.0-dev branch to use it. This means: - third_party can now contain your own libraries, models, helpers to be shared across your modules, themes, widgets, etc without tainting application directory. - 1/3rd less memory usage (not 100% confirmed, but it's quicker). - Less MY_ libraries in application as many of the bugs we had fixed with extended libraries are fixed in the core. - General kudos, not many open-source projects have the balls to do this. We realize that CodeIgniter 2.0-dev is not stable, but every bug we come across will be fixed and sent to EllisLab via their BitBucket repository, so this switch will actually help speed up the stable release of CodeIgniter 2.0. |
||
| Quote | |||
Posted: 2010-05-13 |
# 1 | ||
User
|
Does this mean the PyroCMS v1.0 will be released once CI 2.0 is completed or will we get Pyro before? | ||
| Quote | |||
Posted: 2010-05-13 |
# 2 | ||
|
Admin
|
PyroCMS v1.0 will be released when it's ready, we won't let a final release of CI hold us back as we have no idea when that will be. CI 2.0 is fairly stable now so as long as Pyro is tested well it should be fine. | ||
| Quote | |||