the possibility to build the ComplianceAsCode/content project on RHEL6
using python2.6 and other dated utilities is becoming a luxury. It
prevents contributors to use elegant constructs available in python2.7,
and sometimes passing the CI for RHEL6 requires some weird workarounds
that take time to design and implement and those workarounds just
complicate the code, they don't bring benefits.
As RHEL6 won't get any significant updates and one can build RHEL6
content on other OSs (or in a container), the RHEL6 CI setup seems to
gain negative value. Do you, our precious community around the project,
have arguments why the RHEL6 should be part of the CI?
If there are no agreed-upon reasons, we are leaning towards switching
the RHEL6 CI off within two weeks, i.e. in the first half of March.
On behalf of the Brno Security Compliance team,
scap-security-guide mailing list -- email@example.com
To unsubscribe send an email to firstname.lastname@example.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://email@example.com