We have been in feature freeze since the beginning of the Beta program on June 24th, over 6 weeks ago with only those planned additions introduced as part of Beta2 on July 21st, almost 3 weeks ago. If you’ve kept track of the 2.3 Bug Reports you will know that our bug count is effectively non-existent. With such a low bug count we are tempted to go straight to a final release but since this project is your telephone system, we will run it through the Release Candidate phase and see if there are any last bugs that get flushed out before making it official.
Here’s a quick rundown of where things are at the time of this writing. Beta2 has had about 1350 Beta sites, many of whom upgraded from Beta1. There are currently 6 bugs open and we have closed 208 other bugs. The majority of 2.3 bugs were pulled forward from the 2.2 release and although we have back ported some of those bugs, there are many that have only been fixed in FreePBX 2.3 – making it a more stable release when we go final! We have continued to see a fairly even mix of Asterisk 1.2 and Asterisk 1.4 sites during the testing. This testing has shown that Asterisk 1.4 continues to have some issues and although fairly stable, Asterisk 1.2 is still the platform of choice for at least another few of their releases. However – we sincerely hope that our program has helped the Asterisk community see a large increase in exposure to their 1.4 release.
Since we have been in feature freeze there is not a whole lot of exciting things to announce about this Release Candidate. It represents a step up in our confidence that this will be the final release so if you have not taken the plunge, go try it now.
Internet Explorer Issues
The one Achilles heal continues to be Internet Explorer which is buggy and non-compliant and represents quite a challenge to support as the features and styling of our product evolve. This has been an on going issue since FreePBX 2.2. If you must use IE, you should plan on IE7 because there are some serious problems with IE6. We would like to appeal to the Open Source Community out there if there is someone who is very experiences in CSS on IE platforms and might help us take a look at what can be done to work around some of these issues that are limited to IE problems and bugs.
For now go into Module Admin and upgrade to the next FreePBX Framework Module, which will bring you to RC1. If you don’t have a current install or need to go the old install_amp route, you can follow the instructions below.
Installation should be no different than in the past, whether upgrading from an earlier release or installing from scratch:
- Make sure you are logged in as root; get the tarball, unpack it and install it on your system with install_amp. Then make sure Asterisk is running.
- Go to Module Admin and install or upgrade any modules that need attention
- Start testing and reporting bugs as needed
tar -zxvf freepbx-2.3.0rc1.tar.gz
./start_asterisk # start asterisk if new install, if upgrade use 'amportal start'
./install_amp --force-version 2.2.2
Enough of your time, thanks for reading, go try it out and tell us what you think. Come back and post your comments!
–Philippe (on behalf of the FreePBX Team)