The team has been working hard to fix issues and bugs reported by the community - and a second beta release of CiviCRM 2.0 is now available for
download on SourceForge.
We strongly encourage folks to download and test the beta. If you have an existing CiviCRM install - please upgrade a test copy of your site. Your efforts are critical to help ensure a smooth transition and a quality final release.
We especially need folks with existing Joomla installs to (re)test the upgrade process as we've fixed a number of issues there.
If you've already installed the initial 2.0 beta distribution - and have reported issues - please take the time to install beta 2 and verify that your issues have been resolved.
There were no database changes from beta 1 to beta 2 - so you can simply over-write the beta 1 codebase.
I've included a listing of the 30 issues which were resolved between beta 1 and beta 2 below. You can see the
current list of remaining open issues here.
New 2.0 Installations
If you are installing CiviCRM 2.0 Beta from scratch, use the installation instructions linked below:
Upgrading from 1.9 to 2.0
If you are upgrading an existing 1.9 site (working with a copy of the site, of course), we have provided a browser-based database upgrade script. Instructions for upgrading are here:
If you are working with a database that was initially created prior to 1.9 - be sure to follow the steps to
Ensure Schema Integrity that are included in these instructions.
If you've already installed the first 2.0 beta - there are no database changes from beta 1 to beta 2 - so you can simply over-write the beta 1 codebase.
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.0 feature - or you're seeing a problem and you're not sure if it's a bug - please post your issue to the
2.0 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.0 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.
Resolved Issues - Beta 2
http://issues.civicrm.org/jira/browse/CRM-2498
http://issues.civicrm.org/jira/browse/CRM-2597
http://issues.civicrm.org/jira/browse/CRM-2640
http://issues.civicrm.org/jira/browse/CRM-2641
http://issues.civicrm.org/jira/browse/CRM-2642
http://issues.civicrm.org/jira/browse/CRM-2643
http://issues.civicrm.org/jira/browse/CRM-2645
http://issues.civicrm.org/jira/browse/CRM-2646
http://issues.civicrm.org/jira/browse/CRM-2647
http://issues.civicrm.org/jira/browse/CRM-2648
http://issues.civicrm.org/jira/browse/CRM-2649
http://issues.civicrm.org/jira/browse/CRM-2650
http://issues.civicrm.org/jira/browse/CRM-2652
http://issues.civicrm.org/jira/browse/CRM-2653
http://issues.civicrm.org/jira/browse/CRM-2655
http://issues.civicrm.org/jira/browse/CRM-2663
http://issues.civicrm.org/jira/browse/CRM-2665
http://issues.civicrm.org/jira/browse/CRM-2666
http://issues.civicrm.org/jira/browse/CRM-2671
http://issues.civicrm.org/jira/browse/CRM-2672
http://issues.civicrm.org/jira/browse/CRM-2674
http://issues.civicrm.org/jira/browse/CRM-2677
http://issues.civicrm.org/jira/browse/CRM-2679
http://issues.civicrm.org/jira/browse/CRM-2682
http://issues.civicrm.org/jira/browse/CRM-2683
http://issues.civicrm.org/jira/browse/CRM-2684
http://issues.civicrm.org/jira/browse/CRM-2687
http://issues.civicrm.org/jira/browse/CRM-2689
http://issues.civicrm.org/jira/browse/CRM-2690
http://issues.civicrm.org/jira/browse/CRM-2693
