Announcing 2.2 Stable Release

Pubblicato
2009-03-12 13:46
Written by
Dave Greenberg - member of the CiviCRM community - view blog guidelines
After more than 5 months of design, development and QA - the team is thrilled to announce the release of CiviCRM 2.2 Stable. You can download the release AND / OR try it out on our public demo site. 2.2 features a number of exciting new features, including... You can find Release Highlights here. A big round of applause is due to all the folks who downloaded, tested and submitted bug reports during the 2.2 release cycle. The alpha and beta packages were downloaded more than 4,000 times . Several hundred bugs and "improvements" were reported by community members and fixed by the team during the release cycle.  

Download

You can download CiviCRM 2.2 at our download page. Select from the civicrm-stable section. The filenames include the 2.2 label: civicrm-2.2.0…. Be sure and download the correct version for your CMS (Drupal / Joomla! / Standalone).  

New 2.2 Installations

If you are installing CiviCRM 2.2 from scratch, use the installation instructions linked below:  

Upgrading to 2.2 Stable

If you are upgrading an existing 2.1 site (working with a copy of the site, of course) OR from an earlier version of 2.2 (alpha or beta releases), 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 about installing, upgrading and / or using 2.2 features - or you're seeing a problem and you're not sure if it's a bug - please post your issue to the applicable section of the Community Forum. Include as many specifics as possible about the issue or question. Bugs should be reported via our issue tracking system. Please select 2.2 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 queue.