The team is excited to announce the release of CiviCRM 3.4.8 and 4.0.8. This point release has quite a few bug fixes as listed here. Some of recently added features have been included in the last release blog post
If you haven't upgraded to a 3.4 / 4.0 series release yet, you may want to review the 3.4/4.0 highlights post
CiviCRM 3.4 and 4.0 bring you a new and improved API 3, designed from scratch by non-core CiviCRM developers (i.e., people who actually use the API calls on a daily basis). Your existing code utilising API 2 calls should still work, but you’re more than encouraged to test and upgrade it to the new API 3 calls – API 3 is the one that will be developed in the future, while API 2 will only receive critical fixes.
As per this blog post from few months ago, some multilingual data was turned back into monolingual. You will be informed about this during the upgrade process, but do make sure you have a proper backup of your pre-upgrade database, as only the contents for the default language will be preserved.
The moment of releasing CiviCRM 3.4 and 4.0 is a great occasion to get involved in CiviCRM community. There are many ways you can help make CiviCRM better.
You can download the release from SourceForge. The filenames include the 3.4.8 and 4.0.8 labels, e.g. civicrm-3.4.8-drupal.tar.gz or civicrm-4.0.8-joomla.zip. Make sure you’re downloading the correct version: for Drupal or Joomla. Again, remember that 4.0.x works with Joomla 1.6 and Drupal 7, while 3.4.x works with Joomla 1.5 and Drupal 6.
If you are installing CiviCRM 3.4.8 or 4.0.8 from scratch, please use the corresponding automated installer instructions:
The procedure for upgrading is described in following documents: