Thank you for the response, @gorbak25! 
Follow-up question: Is there anything we can do with version 5.2 to get back on track?
Background: We have been stuck on 5.2 for the last months, because that is the last version that supports the OpenPOWER architecture, which is currently the only Open Hardware architecture that follows the principle of security by transparency, auditability, no hidden management engines or backdoors.
It is also really strong for cloud applications, and has a lot of Hardware Security benefits with its pluggable OpenCAPI interfaces.
There is even a secure workstation available for it: Raptor Computing Systems::Talos™ II Secure Workstation
TL;DR: OpenPOWER is the only hardware architecture that actually follows the principles of user control, security, trust, privacy of aeternity, blockchain in general, and Vereign.
Since IBM acquired Red Hat, it is also fully supported and a primary choice for the entire OpenShift & Cloud platform across a lot of major companies.
Unfortunately, aeternity nodes above version 5.2 fail to build on POWER hardware, due to their dependency on GitHub - herumi/mcl: a portable and fast pairing-based cryptography library and we also had to patch GitHub - aeternity/aecuckoo to get it to compile and run.
The latter is something we would happily contribute upstream, but MCL is not something we can do anything about, unfortunately. We’re right now considering to bring up an up to date node on Intel, but it’s definitely not our preferred choice.
Hence the question: Is there anything we can do with version 5.2 to get back on track?