We’re happy to announce the maintenance releases 3.7.7 LTS and 3.10.3 LTS today!
3.7.7 LTS and 3.10.3 LTS, being maintenance (aka patch) releases, the goal is to increase stability and reliability for CFEngine users and enable a safe upgrade-path. As such, these releases primarily includes bugfixes and low-risk changes that do not impact the compatibility between previous patch releases.
Looking at the CFEngine release schedule, we can see that
- 3.7 LTS is maintained (and supported for Enterprise customers) until July 17th 2018
- 3.10 LTS is maintained (and supported for Enterprise customers) until December 27th 2019
If you are planning to contribute features or fixes to the next minor release 3.12.0 (thank you!), please note that we would need the pull requests ready for merging by the end of February 2018.
Want to start contributing but unsure how?
Improvements and fixes
Automatic reload of def.json (aka. augments file) in cf-execd has now been fixed, so when you make changes here cf-execd will pick them up without a process restart. There are several improvements to package management in masterfiles. The systemd integration has received several fixes, for example to ensure that no processes created by CFEngine are affected by managing the CFEngine systemd units. In 3.10.3, inventory support for Xen hypervisors and Alpine Linux has been improved further.
In CFEngine Enterprise, you can now easily graph and report upon the policy version distribution across your hosts, as the Policy Release ID is inventoried and thus available out-of-the-box in the Mission Portal Inventory report. Use of the Enterprise APIs is made easier, as malformed API requests are explicitly flagged in the responses. The maximum length for Mission Portal passwords has been increased to 100 characters, for those who prefer passphrases. On the scalability side, the database tables can now hold much more data as they now use a larger field for the ID column, which is helpful if you are merging databases from several hubs into one for reporting purposes. Environments with less reliable network can enjoy more reliable report collection with a default timeout for report collection (cf-hub) of 30 seconds, increased from the previous 10 second limit.
As usual, dependencies have been upgraded in order to get the latest security, performance and reliability improvements.
Read the full release blog post on CFEngine.com