Hi i want to ask some thing about the future of fuelphp because i am going to start a long term project in it. Will the future versions of the fuelphp architecture will be same and updates can be done only be replacing the core files without touching the application folder? Or It will be like the kohana? new coding convention and new documentation ( its so frustrating to upgrade the project to new version).
Basicly it comes down to this:
Version numbers: x.y.z
1.0.z = bugfixes & security fixes
1.y = small api changes, mostly nothing that can't be fixed by a project-wide find/replace
x.0 = full new version, everything may change
Any method that is removed or renamed will remain in Fuel for at least one more minor (1.y) release and give warnings in logs about the deprecation. BC for the old usage is only broken in the .y after the release in which it's deprecated.
Also note that while the API stays the same between .y versions, protected methods might change and thus core extensions may need more editing.
More on branching and bugfix/security releases: http://fuelphp.com/blog/2011/08/new-git-branches-and-previous-release-support
Donate
