We are excited to announce that the initial Alpha release of 2.1 is now available for download, AND to try out on our sandbox site. We're really excited about all the cool new features and improvements. Check out Dave's last blog for some highlights... or the 2.1 Roadmap for a more complete listing.
We strongly encourage folks to download and test the alpha release and help improve the final product. Upgrading to 2.1 requires a simultaneous upgrade of Drupal to 6.3, and we need test-drivers who can help us iron out any bleeps or burps that we haven't discovered in our own testing. You can contribute significantly to the project by testing the upgrade process against a copy of your 2.0 data, as well as running your regular tasks on an upgraded site.
Download
You can download CiviCRM 2.1 Alpha at
our download page. Select from the
civicrm-latest section. The filenames include the 2.1 Alpha label:
civicrm-2.1.alph…. Be sure and download the correct version for your CMS (Drupal or Joomla).
As announced previously, 2.1 and all subsequent versions of CiviCRM require PHP 5. PHP 4 is no longer supported.
New 2.1 Installations
If you are installing CiviCRM 2.1 from scratch, use the installation instructions linked below:
Upgrading from 2.0 to 2.1
If you are upgrading an existing 2.0 site (working with a copy of the site, of course), we have provided a browser-based database upgrade script. Instructions for upgrading are here:
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 2.1 features - or you're seeing a problem and you're not sure if it's a bug - please post your issue to the
2.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 2.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.
