At the beginning of this year I announced the intention of the LTS team to support 4.6 as the next LTS and we are committed to keeping 4.6 secure until one year after we stopped supporting 4.4 - ie. the end of January 2017. As with 4.4 the level of support will tail off as key contributors move off 4.6. At this stage we are still getting a large number of fixes for 4.6 and expect to see monthly point releases continuing for the rest of the year.
We have replaced the 4.6.17 release with a 4.6.18 release. This addresses some 4.6.17 regressions that notably affect CiviVolunteer and the estimating groups count on the mailing screen. There was also a pdf creation related error. The issues are to do with 4.6.17 security backports from 4.7 that missed something out.
If you have not yet gotten the security fixes in 4.6.17 you should choose 4.6.18.
Inspired by a colleague I suggested we report today's sprint events in Haiku. Here are the burnt offerings from Colarado!
Bugs & QA team
Many Civi Bugs
Ate the sprinters pesticide
And died horribly
In line with tradition (confirmed by exhaustive research and returning code sprint attendees) I have been tasked with the typical initiation duty of writing a blog post about my first CiviCRM code sprint, specifically the first day. This year's Code Sprint took place early June in Fort Collins, Colorado.
2nd june 2016. we organized the first Budapest CiviCRM Meetup. Unfortunately the attendance was low. We discussed the state of CiviCRM in Hungary, as now only 25 sites registered and 21 uses in Hungarian language. Spent some time on the modules, shared our thoughts. Next Budapest CiviCRM Meetup will be in September this year.
This year we had the second CiviCon in North West Europe, which was in Woerden this year, a small town near Utrecht in The Netherlands.
The latest release of CiviCRM 4.6 and 4.7 includes security fixes. We recommend upgrading to 4.7.8 or 4.6.17 to ensure the security of your site and data. The latest releases include 2 moderately critical fixes. A number of other non-security issues have also been fixed in the latest releases.
In late 2009, we were looking for a better solution for one of our larger faith-based clients. The AMS and CRMs we investigated were either too expensive or too simplistic. We had taken a hard look at CiviCRM about a year earlier, but we didn’t think it was ready. However, with the release of CiviCRM 3.1, CiviCRM was more mature and gave us the flexibility and Drupal integration we needed. CiviCRM was ready and so were we.
Anyone who has tried to login to their CiviCRM database via their phone knows the feeling: utter helplessness. You would even be forgiven for thinking CiviCRM is actively hostile to the small screen.
