We just released CiviCRM 3.3.alpha2 – it is now available for download. You can also try it out on our sandbox site. Please remember this is an ALPHA release and it should NOT be used on production sites.
We strongly recommend going through 3.3 highlights post, where you will find out what’s new and hot in this release.
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.
- 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.