WordPress 2.5 Delayed a Week: According to this milestone in the WordPress Trac, 2.5 is delayed by a week or even more. There is a lot of work being done on styling, bug fixes and open tickets and even though the milestone is delayed to 3/17/08, a well polished release will be more appreciated and will be better for the community than a rush to release.
In the meantime, Lorelle is tapping her feet waiting for the new release and Six Apart is trying to make waves in the wake of WordPress 2.5. Ozh is happy to have the chance to fix some more plugins, Tadd provides some sage advice to people complaining about the wait. I am very excited about this release and what it brings to the table and will be upgrading as soon as I can.
While we are on the subject, in reading through the comments left on Jeff’s post yesterday, we hope we did not cause any added confusion to the impending release. WordPress has gotten more complex since the 1.2 days but that is expected of code reaching a higher level of maturity. However, along with the complexity, WordPress has also gained much anticipated features, has been keeping up and in many cases, leading publishing technology and has become a beacon of success in the blogging and Open Source communities. A lot of the technology that is in 2.5 never existed back when WordPress was forked out of b2 and much of the code and many of the advances have come about due to the hard work of the developers, contributors and supporters of WordPress. Hundreds of developers, contributors and well wishers help shape WordPress and the community is in a very large part responsible for the wonderful peice of software it is today.
The WordPress developers have a feel for their code and they will know when they are ready to put it into production/release. This model creates some confusion because of the nature of the development cycle, but the delaying of the release date and the tweaking and fixing till a comfort level is reached, is not a bad thing at all. On the contrary, if followed with due diligence and with care, this development model can help put together some really good code and it works well in the Open Source (or any shared development) environment. Strict deadlines are more detrimental than a constant update model which has been proven to be more productive and easier to manage.
I have observed and participated in WordPress development from close and afar for many years and though the development cycle might seem disconcerting, I can safely tell you that this effort will bear delicious fruit for sure.
Thanks for being a user and a supporter of WordPress. Here is to a successful WordPress 2.5 in the coming weeks!