The cake is still rising
Recent weeks have seen a few changes in the development team, as well as some clarification of the roadmap for CakePHP future releases. We'd like to thank those leaving for all their hard work and contributions. For those sticking around, you're in for a treat!
CakePHP Project Manager Garrett Woodworth and Developer Nate Abele have left the CakePHP development team. The entire team would like to thank them for their amazing work and efforts towards the core, cultivating the community and various other contributions associated to ongoing CakePHP development. We don't feel that we can fully express the gratitude we have for all their hard work, so we won't. Nate and Garret you will both be missed, thanks for all the fish.
While CakePHP 1.3 is still in development, we're hearing reports of project cropping up using the 1.3 core with great success. This is a testament to the rigorous testing regime in place for 1.3 and the upcoming 2.0 branch of code.
CakePHP 2.0 development has picked up significantly, being led by Predominant (Graham Weldon) and PhpNut(Larry Masters). A push is being made to release a "development" release as soon as possible. The rough roadmap and feature set of the CakePHP 2.0 branch has been updated on the CakePHP 2.0 wiki[1]. We're all excited to see more user input and feedback on the CakePHP 2.0 development and plans.
So, while we've had changes in the development team recently, in terms of the active developers working on CakePHP current branches, very little has changed. We'd also like to extend a thanks to Matt Curry[2] for providing a fill-in-the-blanks reply, to all the end of the world comments floating about.
[1] http://code.cakephp.org/cakephp2/wiki
[2] http://pseudocoder.com
The CakePHP team
Where does that leave us?
Recent efforts have seen CakePHP 1.3 being developed primarily by Mark Story. Mark has taken the lead on this version, and has been steam rolling bugs and plucking out enhancements for this version. Phenomenal progress has been made on the 1.3 branch, and we're all excited to see the progress.While CakePHP 1.3 is still in development, we're hearing reports of project cropping up using the 1.3 core with great success. This is a testament to the rigorous testing regime in place for 1.3 and the upcoming 2.0 branch of code.
CakePHP 2.0 development has picked up significantly, being led by Predominant (Graham Weldon) and PhpNut(Larry Masters). A push is being made to release a "development" release as soon as possible. The rough roadmap and feature set of the CakePHP 2.0 branch has been updated on the CakePHP 2.0 wiki[1]. We're all excited to see more user input and feedback on the CakePHP 2.0 development and plans.
So, while we've had changes in the development team recently, in terms of the active developers working on CakePHP current branches, very little has changed. We'd also like to extend a thanks to Matt Curry[2] for providing a fill-in-the-blanks reply, to all the end of the world comments floating about.
[1] http://code.cakephp.org/cakephp2/wiki
[2] http://pseudocoder.com
The CakePHP team
Comments
Comment
1 Cake3 status?
If that is the case, I think it'd be for the better of both projects. Going from 1.2->1.3->2.0 seems like a pretty clear path. I never really knew where Cake3 fit in.
That said, Cake is being held back by PHP4. You guys are solving this through refractoring. And Cake3 was solving that with a rewrite.
Choice is a good thing for developers.
Comment
2 Cake on
Really looking forward to baking some more cake.
Comment
3 breaking up is hard to do
Mark, thanks for communicating this to us. Your commitment to 1.3 is obvious.
Comment
4 High goals and a long way to go.
Short in english:
lithium = High goals and a long way to go.
Cake1/2 already excelent code quality and broad support by plugins.
It is now a good point to take an active part at the Cake commuity!
Comment
5 good times
Comment
6 Santa Mark
Garrett: I will miss your brain in project timeline, your helpful hands in every possible occassion, your opinions on the life, universe and everything. I am sure it was hard decision and you have good reasons. Let me hope you will find your way back one day... Best wishes, thanks for all the fish and good luck with your new toy!
Nate: thank you for your resignation and for letting us alone in the world where only best interests of The Project matters. I think your resignation is one of most good things you did for cake in recent months. Once again: thank you for behaving the same as usually: dropping the ball on things. This time, I really do appreciate that. I assume that now we can agree on few things I've said to you before: a) namespaces-only code is not close future of CakePHP, b) cake3 is wrong name for this project and c) splitting team and let part of it work on something in secret is not good for team spirit. I am not saying everything you did was bad (although we both knows how long would be list of stupid things you can still blindly fight for); I am saying you were doing things against CakePHP best intererests for a long time and your resignation is just end of short episode in CakePHP history - times, when Lead Developer acted against core team and The Project itself. I'm not sure I can thank you enough, and I am not sure how long you planned this step. You're very good in politics, probably even better then in coding. If ego could help with coding, you are The One. Fortunately, it doesn't matter to CakePHP any more.
I can not wait to contribute something; again without feeling it is unappreciated wasted time. I will keep fingers crossed so we can get back our lost souls who left us or stopped contributions/donations because of ego fights in the core team, when people (using plural is maybe not correct) were trying to prioritize promotion of their names over code and community needs. Clouds are away, now it will be (again) pleasure to work.