CiviCRM v3.1 Beta 4 Released!!!

The fourth BETA release of version 3.1 is now available for download. You can also try it out on our sandbox site. Check out release highlights here!. (Please remember it’s a beta release and it shouldn’t be used on production sites.)  

Step up and help out!

Beta releases are a great occasion to get involved in CiviCRM community. There are many ways you can help make this release better and bug free.

• Log in to the CiviCRM 3.1 public sandbox and try out your favourite features. If you find a problem, please report it on the appropriate forum board. Remember that sandbox data is periodically reset.
• Download the tarball and upgrade a copy of your site to 3.1 - let us know if you encounter any problems. This is an especially valuable contribution since we need to have the upgrade process tested on different sets of data. After you've done this, play around with your favourite features, with your local data. Problems appearing? Use the CiviCRM 3.1 release testing board on the forums to discuss problems and find answers!
• If you're a developer and have PHP skills, we strongly encourage you to develop and attach a code patch AND a unit test along with any bug you report through our issue tracker. Ping us on IRC if you need help figuring out how to do this.

 

Download

You can download CiviCRM 3.1 Beta 4 from the "civicrm_latest" section. The filenames include the 3.1 Beta label: civicrm-3.1.beta…. Be sure and download the correct version for your CMS (Drupal or Joomla) or Standalone.  

New Installations

If you are installing CiviCRM 3.1 Beta 4 from scratch, please use the 3.0 versions of the automated installer instructions (the installation process has not changed):

• Drupal
• Joomla
• Standalone

 

Upgrading 2.2.* or 3.0.* Sites to 3.1 Beta 4

An automated upgrade process is included in the beta release, and the procedure for upgrading to 3.1 beta 3 is the same as for upgrading to 3.0.x. You can upgrade directly from 2.2.x, 3.0.x, or earlier 3.1 releases (alpha's or beta's). Instructions:

• Drupal
• Joomla
• Standalone

 

Reporting Issues and Bugs

We look forward to getting your feedback on the release in the coming days. If you have questions installing, upgrading and / or using 3.1 features - or you're seeing a problem and you're not sure if it's a bug - please post your issue to the 3.1 release testing section of the community forums. Include as many specifics as possible about the issue or question. Bugs should be reported via our issue tracking system. Please select 3.1 in the ‘Affects Version’ dropdown. You will need to register as a user – this ensures that we can follow-up with you on your bug reports if necessary. Please ensure that the bug you’ve found is not reported already by checking the open issues listing. We will continue to include automated upgrades for subsequent beta and stable releases of 3.1 - so you should be able to upgrade your test site easily over the course of the release cycle.