Stable is getting closer and closer, as proved by a second pair of betas for CiviCRM 3.4 and 4.0!
An remember - if you didn't already, make sure you read "Step up and help out" section of this blog post!
The newest versions are:
Please remember this is an BETA release and it should NOT be used on production sites - however, we enourage you to install it on your test sites and let us know about any bugs or problems. If you want to find out what's the beta/final release schedule - it is available on our wiki.
There are a few public sandboxes where you can try one (or many) of above versions:
Feel free to click around and let us know what you think.
The moment of releasing CiviCRM 3.4.beta2 and 4.0.beta2 is a great occasion to get involved in CiviCRM community. There are many ways you can help make this release better and bug free.
Quick list of the most prominent new features and improvements in this release:
and other features, sponsored through successful Make it Happen campaigns:
More details on the new features are in the Whats new in CiviCRM v3.4 / v4.0? post
You can download the release from SourceForge - select from the civicrm-latest section. The filenames include the 3.4beta2 and 4.0beta2 labels, e.g. civicrm-3.4.beta2-drupal.tar.gz or civicrm-4.0.beta2-joomla.tar.gz. Make sure you're downloading the correct version: for Drupal or Joomla. Again, remember that 4.0 works with Joomla 1.6/Drupal 7 and 3.4 works with Joomla 1.5/Drupal 6.
If you are installing CiviCRM 3.4.beta2 from scratch, please use the corresponding automated installer instructions:
The procedure for upgrading is described in following documents:
We will continue to include automated upgrades for subsequent alpha and beta releases of 3.4/4.0 - so you should be able to upgrade your test site easily over the course of the release cycle.