SYNOPSIS:
Does this version...? |
|
Fix security vulnerabilities? |
no |
Change the database schema? |
no |
Alter the API? |
no |
Require attention to configuration options? |
no |
Fix problems installing or upgrading to a previous version? |
no |
Introduce features? |
no |
Fix bugs? |
yes |
ISSUES RESOLVED:
This version reverses an update made in the 4.6.33 release adding pre and post hooks for recurring contributions. The update caused regressions for some people who implemented the pre or post hooks for customizations for contributions.
SPECIAL THANKS:
Thanks to Skvare and Compucorp for maintaining the CiviCRM LTS Version.
A full list of contributors can be accessed here.
WHY LTS IS IMPORTANT:
Keeping the stability of the CivCRM LTS version of CiviCRM continues to be important to consumers as there are still many sites actively running the 4.6.X branch.
In 2017, only a few lines of codes have been changed to improve security and fix bugs, proving that maintaining a LTS version is a top priority. The PR issue queue has been cleaned up and 14 PR’s have been processed this year:
https://github.com/civicrm/civicrm-core/pull/10408
https://github.com/civicrm/civicrm-core/pull/10411
https://github.com/civicrm/civicrm-core/pull/10409
https://github.com/civicrm/civicrm-core/pull/9855
https://github.com/civicrm/civicrm-drupal/pull/451
https://github.com/civicrm/civicrm-drupal/pull/450
https://github.com/civicrm/civicrm-core/pull/11178
https://github.com/civicrm/civicrm-core/pull/11179
https://github.com/civicrm/civicrm-core/pull/11176
https://github.com/civicrm/civicrm-core/pull/11174
https://github.com/civicrm/civicrm-core/pull/11174
https://github.com/civicrm/civicrm-core/pull/11180
https://github.com/civicrm/civicrm-packages/pull/195
https://github.com/civicrm/civicrm-core/pull/11177
Future of LTS
In 2018, we will continue to maintain CiviCRM 4.6 LTS. With the PHP 5.6 end of life approaching in December 2018, having a LTS version that supports php 7.1 and MySQL 5.7 will become critical. To continue the ongoing success of CiviCRM LTS, support from the community is needed. Get involved by visiting https://issues.civicrm.org, or contact Skvare.