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.
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.
Along with the introduction of CiviMail Processor as the new supported return email hander, we’ve made three changes that are relevant for third-party CiviMail developers in CiviCRM 2.2.
Unified email formats