Update: Due to an unfortunate error multilingual sites cannot be upgraded to CiviCRM 3.2.2; if you’re running such site please wait for CiviCRM 3.2.3. Single-language sites (regardless of the language they use) should upgrade to CiviCRM 3.2.2 cleanly, and new CiviCRM 3.2.2 installations (both single- and multilingual) should work without a problem.

As you have already read in the previous blog posts, one of the outcomes of the translation sprint is the fact that we’re switching our translation server to a new tool, Transifex.

We decided to go with Transifex for various reasons:

• Transifex allows teams of people to collaborate on translations – this is not an issue when you have a single person working on a translation, but as soon as you have two or more contributors working remotely, it’s crucial to use a tool that streamlines the process and allows for easy and centralised communication,
• the user hierarchy is simple, clean and seems to be efficient: project maintainers accept language maintainers who, in turn, accept language team members and coordinate given language’s development,
• project maintainers can announce localisation-oriented things on the project’s page,
• teams can have discussions on the per-language discussion boards,
• the user interface for translations is better and easier to work with, and has the (dubious for some languages, but useful for others) ability to fetch Google Translate suggestions on-the-fly,
• PO files can be locked for work in offline tools (like Poedit, Virtaal or others) and the locking is visible to other contributors.

Two weeks ago Michael McAndrew, Xavier Dutoit and me (Piotr Szotkowski) had the pleasure to attend Campaigning Camp 2010, hosted by FairSay in Oxford, UK. Campaigning Camp was a two track event, with concurrent CiviCRM and Plone development sprints interspersed with general campaigning advice from FairSay’s Duane Raymond.

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.