Sprinting in New York City

Last week saw the first CiviCRM sprint in New York city. For those new to the community or open source software sprints are probably a bit of a strange concept. I know I sometimes struggle to explain them to border control agents as I enter the US.... But really a sprint is just a way to take time out of your day to day work life to learn, meet people and collaborate and to see a bit about how CiviCRM works behind the scenes.

Continuous Extension Integration

What?

CiviCRM core now offers a Continuous Integration service to partner & member organisations on their extensions. The service will run the unit tests associated with an extension whenever a PR is submitted to that extension. This is similar to the process that runs on core and is driven by jenkins and runs on the same test infrastructure. There are free services that do this (e.g Travis) on github in general but they don’t provide the CiviCRM setup and database environment that is needed to run tests on CiviCRM.

 

Product maintenance in CiviCRM

As our North American colleagues (and those who have made the big trip over there) head into the governance sprint now seems like a good time to recap on product maintenance in CiviCRM. Product maintenance, as I discuss, is the monthly routine processes we do to incorporate patches & contributions into the CiviCRM product. This blog is kinda long & weedsy - so if it’s not for you then take a look at this baby octopus instead.

 

End of life plans for 5.x php versions & planning for 7.0 EOL

This blog serves as advance notice of our intention to stop supporting php versions 5.5, 5.6 and our ongoing evaluation of 7.0.
 
For php 5.5 we intend to end support in January 2019.
This is already unsupported by php and we strongly recommend you upgrade off it as soon as possible. The release in February 2019 will be the first release that does not support php 5.5
 
For php 5.6 our TARGET is to end support in September 2019 (Oct release would support php 7.0+).

Who did what when?

For many years CiviCRM has had the capability to log all actions that take place in the database but while it mostly works well there have been a few issues. I looked into these recently and came up with some improvements, which shipped in 4.7.7 - but if you want to take advantage of them there are some actions you might need to take. This article is mostly intended for a technical audience.

 

How does CiviCRM logging work?