In a new post, Greg Beaver talks about a few things, the main one being a new release of the phar extension he's made - phar version 2.0.0a1 - a reworking of the previous functionality with loads of new features including:

• Phar now supports tar and zip archives with the same API that is supports phar archives.
• Phar has a front controller for web applications that fully handles MIME types, supports mod_rewrite-like functionality with far more flexibility
• Phar supports phar:// stream wrappers in include_path for PHP 5.2+
• Phar supports creation and modification of data-only tar and zip archives (no executable phar stub) via the PharData class.

There've also been updates to the manual for the project to reflect this new version of its API. You can download this latest version here: source or Windows DLL.

The Symfony project is recommending you upgrade your plugins to the latest editions - an issue with the PEAR channel caused it to load the wrong ones:

A problem in the symfony project PEAR channel made the plugin-install task always install the oldest version of the plugins, instead of the latest. If you recently installed plugins with the symfony command line, you probably installed an outdated version. Plugins installed via SVN are not affected.

You'll need to run a plugin-upgrade command for each of the plugins installed on your system to ensure that you're completely up to date. The post has complete info on how to tell which plugins you have and the exact commands to issue to being them up to date.

The CodeIgniter development group has released the latest version of the framework - CodeIgniter 1.6.1:

Version 1.6.1 is primarily a maintenance release, but does bring a handful of nice feature additions and enhancements. After a very successful 1.6.0 release, a series of bugs have been squashed and enhancements have been made that we wanted to roll out as a formal release.

The update process is just replacing a few files from your current installation. Check out the Changelog for more information on the updates made and, if you're not quite sure what you're doing on the update, check out their handy update instructions.

Marco Tabini (of php|architect) has posted some thoughts to his blog about the PHP4 end-of-life announcement and its relations to the current push to go PHP5 - mainly how it relates to hosting providers.

I'm sure that a large number are owners of small hosting firms - which, by far, provide the vast majority of PHP-powered websites that Netcraft carefully tracks for us - that sell cheap shared hosting. [...] If you provide shared-hosting plans, it's likely that your servers are still running PHP 4. Upgrading to PHP 5 is a logistical nightmare for two reasons: first, you don't necessarily know that you'll be able to properly set up and secure your systems; second, you don't know that your customers' applications will keep on running.

Both reasons can cause very different kinds of hassles for the hoster, especially when it comes to their customers. As Marco puts it "hell hath no fury like a customer scorned". When things are going smoothly, everything's good, but the second that you try to explain that the update is what's good for them, all they see are things breaking and freak out.

He suggests only one real solution - make the move and tell the customers now that things are changing. Help them all you can (with information about updated software and resources) but ultimately it's up to them to make the change.