On the Symfony blog Fabien Potencier has posted about the roadmap to a final release for the Symfony2 version of the popular framework including some of the things that will and will not change after the release.

We are now ready to release Symfony 2.0 final. As we have made some significant changes in the last couple of weeks, we are publishing another release candidate (RC5) today and we will wait for a week before releasing Symfony 2.0 final on Thursday 28th.

The upgrade to Symfony2 is just a few commands away and there's a large list of components that are set and will not be changed moving forward including the DependencyInjection, Finder, Locale, Routing and Validator.

Symfony 2.1 will be the first release with all the components with a public stable API. And for components that already have a public API in 2.0, 2.1 will be the occasion to add even more classes and methods to it.

In a recent post to his blog Matthew Weier O'Phinney shares the state of Zend Framework 2.0 and and the roadmap for the days ahead in the framework's development.

The past few months have kept myself and my team quite busy, as we've turned our attentions from maintenance of the Zend Framework 1.X series to Zend Framework 2.0. I've been fielding questions regularly about ZF2 lately, and felt it was time to talk about the roadmap for ZF2, what we've done so far, and how the community can help.

Included in the roadmap for the upcoming version are things like easing the learning curve for new developers, improving the baseline performance of the framework, an effort to simplify things and to use PHP 5.3 to it's best capabilities.

You can see the full roadmap here.

In response to the recent release of the roadmap for the 2.0 version of the Zend Framework, Giorgio Sironi has posted some comments of his own and the future of the framework and some of the decisions the Zend Framework teem has made.

I already posted some questions on the wiki, but I would like to expand my thoughts on the architectural changes from a testing and design point of views, that are what interest my readers. Here's a list of the guidelines that have the greatest impact.

The touches on a few topics - the unified constructor, ridding the framework of singletons, implementing a design by contract approach, namespacing, changes in the Zend_Session component and a few others.

Content no longer valid

According to this quick post on the Zend Developer Zone today, the Zend Framework project has a new leader to take the place of Jayson Maynard when he left.

After a difficult search, we have found the seasoned veteran we need to track, manage, and coordinate our ever growing group of contributors and Zend liaisons, and our lengthy list of components and sub-projects on our published roadmap for ZF 1.0, and beyond.

Fortunately, we were introduced to Bill Karwin. Bill is up to this challenge, having performed similar project organization duties at several companies, including Borland and Lutris Technologies. He is also committed to the open-source community, and is a member of the MySQL Guild.

Cal has some other nice things to say about Bill, including a compliment on Bill's grasp on the Zend Framework project.

The Zend Developer Zone has republished the latest roadmap for the Zend Framework as posted by Andi Gutmans of Zend.

Although not always visible due to the infrequent release of new framework packages, there has been a lot of progress in the past few months. More than 100 community members(!) have joined the effort by singing the CLA, and are contributing via proposals, comments, patches, code contributions or documentation improvements.

Now the Summer is over and everyone is back at work, we feel it's the right time to finish planning the 1.0 release. We believe that in order to make a successfull release and get closure on the various aspects, it makes most sense to break up the framework into a limited number of subject areas and form project teams around these areas instead of components.

The following is a list of such areas and the components we believe we should focus on for 1.0. As you can see, a large amount of the work has already been done, but we now have to focus on getting closure on them and tying up loose ends.

Some of the components they've listed fall under the categories of:

• Web & Web Services
• MVC & related
• Authentication & authorization
• Databases
• Documentation & translation

There is also a high-level look at what version 0.2 of the framework will contain and a return to the "post often" methodology they had before.

On WebProNews.com a PHP roadmap has been posted - a comprehensive look at what PHP is and how it's evolved.

We expect our readers to have a more than firm handle on what PHP is, but for completeness-sake: PHP (a recursive acronym of PHP: Hypertext Pre-processor) is an open source, server-side web-scripting language for creating dynamic pages.

They look first at what PHP has to offer, then how it's evolved, and finally a comparison of PHP to several other langauges, including Perl, Java, and Cold Fusion.

With all of the turmoil surrounding the PHP 5.1.0 and 5.1.1 releases just fading, there's already talk of the next release in the series - 5.1.2 - and a plan to follow to get there.

Here is a brief outline of how I see 5.1.2 release happening and what in my opinion should be included in the release. This is very much an RFC as far as the changes go, so feel free to comment.

First the release plan, my idea is to allow minor features with accompanying tests that do not introduce any BC issues or functionality regressions till the 10th of December. At this point we would go into a feature and major change lock down, till about 22nd of December when the first RC will be made.

Assuming a 1 week period without such fixes passes, final release will be tagged, making the last RC essentially that release. In the even critical issues are discovered, additional RCs will be rolled.

So, some of the target dates as mentioned above include Release Candidate 1 on Dec. 22nd, Release Candidate 2 on Jan. 5th, and a final of PHP 5.1.2 on Jan. 12th, 2006. You can also check out some of the planned changes as well...