In a month, on March 25th and 26th, FairSay invites you all to Oxford, UK to join us for a two-track CiviCRM/Drupal and Plone Campaigning Camp (free with lunch and tea break included!).

We're preparing a CiviCRM developer camp in Brussels on February 8th and 9th – right after FOSDEM 2010. Developer Camps are a place where CiviCRM developers, administrator and users can get together around CiviCRM. We'd like you to let us know what you want to see at the camp by commenting on the wiki page.

As we’re closer and closer to the release of CiviCRM 3.1, we began thinking what to schedule in CiviCRM 3.2. As one of the features we want to add is the ability to undelete certain CiviCRM entities, we want to discuss with the community the initial approach to undelete that we came up with – along with a sketch of logging functionality that we consider for a future release.

We’re happy to announce that CiviCRM 3.0.beta3 is now available for download. You can also try it out on our sandbox site. Please remember it’s a beta release and it shouldn’t be used on production sites. This might very well be the next-to-last beta before we release 3.0 stable, so if you haven’t checked whether your favourite (old and new) CiviCRM features work the way you expect, it’s a very good time to do it – we will most probably fix only the most important issues for the 3.0 branch after 3.0.beta4 is released next week.

Check out the blog entry announcing 3.0.alpha1 release for a run-down of what’s new in CiviCRM 3.0, and this list for issues that were fixed since 3.0.beta2. A full list of changes, improvements and bug fixes in 3.0 release is also available on the wiki and in the issue tracker.

We’re happy to announce that CiviCRM 3.0.beta2 is now available for download. You can also try it out on our sandbox site. Please remember it’s a beta release and it shouldn’t be used on production sites.

Check out the blog entry announcing 3.0.alpha1 release for a run-down of what’s new in CiviCRM 3.0, and this list for issues that were fixed since 3.0.beta1. A full list of changes, improvements and bug fixes in 3.0 release is also available on the wiki and in the issue tracker.

We’re happy to announce that CiviCRM 3.0.beta1 is now available for download. You can also try it out on our sandbox site. Please remember it’s a beta release and it shouldn’t be used on production sites.

Check out the blog entry announcing 3.0.alpha1 release for a run-down of what’s new in CiviCRM 3.0, and this list for issues that were fixed since 3.0.alpha3. A full list of changes, improvements and bug fixes in 3.0 release is also available on the wiki and in the issue tracker.

We’re happy to announce that CiviCRM 3.0.alpha2 is now available for download. You can also try it out on our sandbox site. Please remember it’s an alpha release and it shouldn’t be used on production sites.

Check out the blog entry on the previous alpha1 release for a run-down of what’s new in CiviCRM 3.0, and this list for issues that were fixed since 3.0.alpha1. A full list of changes, improvements and bug fixes in this release is also available on the wiki and in the issue tracker.

As mentioned previously, we’re introducing quite a few new CiviEvent features in CiviCRM 2.3. Most of them are still undergoing our internal CiviCRM QA cycle, but do check them out at our CiviCRM 2.3 sandbox if you’re interested (there is still time for some minor fixes to accommodate your use-cases!).

We’ve just finished describing some of the new CiviEvent features we’d like to put in CiviCRM 2.3, including waitlisting and optional admin approval of participants. Please take a look at the CiviEvent - New Features for 2.3 wiki page and voice your opinions.

The documentation for CiviCRM 2.2 is up and so are the new docs for CiviMail Installation, including a sub-page on CiviMail Processor.

Please do let us know how to improve these pages (or help even more by doing it yourself!).