cv (https://github.com/civicrm/cv) and
civix (https://github.com/totten/civix) are Unix/CLI tools for developers.
cv provides access to your Civi site on the command line, and
civix generates skeletal code for new extensions. We've had a few recent updates to each of these tools, so I wanted to introduce
cv more formally and then recap some of recent improvements for each tool.
We're pleased to announce availability of CiviCRM v4.7.13 and v4.6.23.
This release was heavily influenced by the contributors from the sprints in Maryland and Edale and benefited from an extended release-candidate period. Combining the efforts of on-site and face-to-face contributions, this release addressed over 100+ JIRA issues and 170+ pull-requests.
At the CiviCons and developer meetings this year, we've had several conversations about release strategy. The topic is a bit abstract -- touching on a web of interrelated issues of technology and scheduling and business-process. I've been searching for a way to explain this topic to people who don't eat and breathe code in CiviCRM's
git repos -- an analysis which is a bit simpler and more transcendent.
The best analysis predates us by a few years -- Will Durant attributed the idea to Aristotle's Nicomachean Ethics, paraphrasing:
Good evening. (Or, for folks in America… good afternoon. For folks in Oceania, good morning.) I'm writing from the CiviCRM sprint in Edale (UK), and it’s the height of apple season. In an ordinary year, the local folks here would be shaking the apple trees, getting a bit tipsy on cider, and discovering gravity. But this year, an influx of visitors from around the UK and Europe (and the broader CiviSphere) have come to make this pastoral setting even more beautiful: it’s the land of PR-review and testing.
The latest release of CiviCRM 4.6 and 4.7 includes security fixes. We recommend upgrading to 4.7.11 or 4.6.21 to ensure the security of your site and data. The latest releases include 9 security fixes and improvements. A number of other non-security issues have also been fixed in the latest releases.
To determine the impact of security fixes and improvements on your system, please review these advisories:
To ensure that CiviCRM continues to work with standard, contemporary PHP hosting platforms, a future version may make a subtle change in hosting requirements. We expect this to be mostly seamless; however, we're looking for administrators responsible for sites running a recent CiviCRM (e.g. v4.7+) to spend a few minutes to help ensure a smooth transition.
Q: I'm not too fluent in geek-speak. What should I do?
Forward this to whoever manages your server. If you work with a CiviCRM partner, they may be thinking of you already.
Automated tests are important when collaborating with other developers in a large project. Even if you focus your attention on a small piece of the puzzle, your piece depends on other pieces, and others may depend on you. There will be inevitable occasions when a change in one causes an unexpected change or break in another. Automated tests form the first line of defense, providing timely feedback so that problems can be addressed while the material is mentally fresh.
Civi v4.7 introduces some overhauls to the core CiviCRM development framework. Some of the planning discussions can be found in the forum, but now that it's merged and stablized a bit, I wanted to give a walk-through for other developers. A few highlights: