[Open-scap] Phasing out the RHEL6 CI

Dear community, the possibility to build the OpenSCAP "oscap" suite on RHEL6 using those dated utilities s.a. python2.6 is becoming a luxury. Sometimes, passing the CI for RHEL6 requires some weird workarounds that take time to design and implement and those workarounds just complicate the cod

Re: [Open-scap] Phasing out the RHEL6 CI

My only concern is that sometimes a government customer will mandate using some flavor of RHEL 6, for whatever reason they may have. For example, we have a government customer mandating we use 6.5 at the moment. And they are perfectly happy to have us STIG the 6.5 OS manually, page by page, if t

Re: [Open-scap] Phasing out the RHEL6 CI

On 2/26/19 12:07 PM, Boucher, William wrote: My only concern is that sometimes a government customer will mandate using some flavor of RHEL 6, for whatever reason they may have. For example, we have a government customer mandating we use 6.5 at the moment. And they are perfectly happy to hav

Re: [Open-scap] Phasing out the RHEL6 CI

I agree with Shawn. From technical perspective - we haven't had special RHEL6 maintenance branch in the github project. It is the same maint-1.2 which was further developed for use in RHEL7. So honestly - whatever is working on current maint-1.2 branch (version 1.2.17) will probably not be triv