Rohan Kapoor

I just released bbPress Favicon the companion plugin to WordPress/MU Favicon. It does exactly the same thing WordPress/MU Favicon does except does it for the bbPress sitewide and the bbPress admin pages. You can see the Changelog for those that are interested!

After being told off by mercime for not having a page for WordPress/MU Favicon, I finally got around to pulling it’s page out of Drafts and updating it to show the latest information regarding version 1.1.

It appears that it took me long enough to pull it together, but hey, I was busy. Anways better late then never.

The homepage for WordPress/MU Favicon is here.

And for anyone interested, here is the changelog:

I released version 3.0 of New bbPress Admin today! This version is mainly a bugfix release with no new functionality. You can see the changelog for more details.

You can view the plugin page here. Or download directly from the WordPress Plugin Repository here.

Currently version 3.0 is the most stable version with no bugs that I know of!

Enjoy

New bbPress Admin was officially updated last week to version 2.0. This adds a lot of stability along with a few other functions. The changelog details more…

2.0

• Second Version of bbPress Admin. It has been adapted to have a backend interface to set the forums directory.
• Looks Neater and is much easier to use.
• Works with WP/WPMU 2.8.2 and bbPress 1.0.1

1.0

• First Version of bbPress Admin. It is very simple and rudimentary at this point.
• Working with WP/WPMU 2.8.1 and bbPress 1.0.1

You can find the plugin at it’s homepage. Right now Version 2.0 is stable however there are a few small bugs that are being worked on! Version 2.1 is in BETA on SVN!

Additionally, the homepage of New bbPress Admin has been updated so that it shows the most recent information (almost identical to the information on the http://wordpress.org plugin page.

Taken from here:

We feel that all software should have a changelog that details, at a high level, what changes have been made in each version so that the user can make an informed decision about when to upgrade and how much testing they should do with their site.

In order to make this an easy and open communication channel we have added support for a Changelog section in the plugins readme.txt file.  This changelog information is then displayed as a separate tab in the plugin directory and also in the back end of your WordPress blog when you view the details on a new version of a plugin.

I personally agree with this decision of the Automattic and the WordPress team because I have found some annoying plugins which don’t state why a plugin is updated. This should solve that problem rather nicely!