If you've been following the CiviCRM blog, you probably noticed the reports from Google Summer of Code 2014: Siddhant Rajagopalan built a new CiviMail composition screen, and Aditya Nambiar built an A/B testing system.
Blog posts by totten
Keep up-to-date with blogs from the core team, working groups, developers, users and champions worldwide. Subscribe to our newsletter to receive regular updates by email. We also have an RSS feed.
Summary
Beginning with CiviCRM v4.6, developing code for CiviCRM (civicrm-core.git) will require two additional tools: Composer and NodeJS. If you develop CiviCRM, then you should install them in order to continue development.
In recent blog posts, we've expanded the long-term support effort to 4.4, discussed the release window (first and third Wednesday of each month), and experimented with release-candidates
There has been a security advisory for CiviCRM. We recommend you immediately upgrade to one of the following versions:
We’ve been having some discussions among the folks who triage security issues, who publish new releases, and who maintain backports. We'll update the policy beginning with the upcoming 4.4.7 release (and related 4.2.19 and 4.3.9 releases).
Good testing is critical for providing quality software. Some testing is always manual but writing automated tests to do the heavy lifting is a key part of modern coding practices. For developers, the discipline of writing automated tests helps to proactively identify and control edge-cases, and regularly running tests helps to identify problems quickly (before they grow and cause greater harm).
There has been a security advisory for CiviCRM. We recommend you immediately upgrade to one of the following versions:
CiviCRM 4.4.6 (latest version) CiviCRM 4.2.17 (LTS)Read the security advisories for details:
Good day, folks, The CiviCRM Partners list recently discussed the topic of release-announcements and release-testing. We'd like to treat 4.4.6 as a bit of an experiment to address two specific ideas about release-management:
CiviCase is a case-management system for tracking multistep interactions with constituents -- such as social support services, constituent services, and applications for employment. The CiviCase toolset enables organizations to provide a more consistent quality-of-service to their constituents by setting out a base timeline for the services to provide to each constituent.
(This post is a follow-up to previous discussions about developing recruitment functionality for CiviHR.
