The open source Web forum application, phpBB, is available in a new version. phpBB 3.0.6 introduces not only bug fixes and stability improvements but also some major new features.
We are very pleased to announce the availability of the phpBB "Fast and Furrious" 3.0.6 package. This release fixes numerous bugs, introduces some major features, as well as improves stability and performance. Furthermore, the internal updater has been updated to detect and solve most conflicts, resulting in a reduction of necessary manual interaction by administrators.
Please note that we urge you to update. phpBB 3.0.6 fixes bugs being quite important for a smooth operation of your forums. With this release our support team will only give support for phpBB 3.0.6, updates to phpBB 3.0.6 and conversions to phpBB 3.0.6. Submissions to our trackers for older versions will not be accepted, please make sure you update/upgrade before you submit a bug report.
Some of the new features that have been implemented in phpBB 3.0.6 include:
Better spam control using improved captcha options and backported 3.2 captcha plugins:
Alex S. wrote to us and and recommended that everyone take a look at MyBB, a Web forum application.
I noticed MyBB isn't on your CMS Focus list. I would recommend you looking into it as it is an amazing system. It even just went open source recently.
But, don't take my word for it KDE is now using it them selves. It's new compared to SMF and phpBB but it's already competing with the best (including IPB and vB).
I'm not a developer or anything. Just recommend this amazing forum system with a bright future.
While I make no promises on getting MyBB into CMS Focus, I do think it is time to take a new look at SMF, phpBB, vB, and the new comers. Perhaps in a couple days we'll see if it is time for another forum application to knock SMF off the top 30 CMS list. May the best forum software win...
Eric @ phpbb.com: "We are pleased to announce the opening of a phpBB Blog. This blog will be written by the phpBB Team on various topics related to phpBB and communities. The blog will provide an inside look into the phpBB Teams while benefiting the community.
When you split the list into three sections, you get the feeling that PHP-Nuke, ezPublish, and osCommerce have been around for a very long time. More importantly, you begin to think that it is time for Gallery, Drupal, and MediaWiki to either be seen as mature applications or for those applications to finally grow up.
Why did we move to phpBB3?
Good question, and there is a simple answer. Whilst SMF was great for
us, it is not licensed under GPL, and as a result many of our users who
like to follow the choices we make were going to run in to integration
issues in the future. As well as that, the team at phpBB have been
great, with many of them offering to help, especially with the
conversion.
In any case, we’re not going back, and the future is phpBB3!
Beyond a few minor tweaks, it looks as if Joomla.org was able to convert SMF over to phpBB with very few issues. Considering the Joomla community forum usually has hundreds of users on line at the same time, this is no small move for a forum to make the switch to new software. Congratulations to Joomla!
Once again, another open source project has dropped Concurrent Versions System (CVS) for Subversion (SVN). Both CVS and SVN are open source version control systems used mainly by developers involved in various software projects. This time the project is phpBB, a forum application.
We like to announce the switch from CVS to SVN for our repository
management and source control. Within this step, we also set up a new
home for phpBB development and phpBB related projects. At the moment
only phpBB itself is listed and only repository management handled
there. Within the next months we will enable more and more features and
move internal projects as well as hopefully other public projects to
the new home. [Link]
Although I'm not much of a developer, I've been interested for some time in why a project has picked one version control system over another. In part this is because I recognize revision control is something my own employer need to do better, not just for the larger projects but even the "local" non-enterprise projects I often found myself involved in.