We should have the CR packages, that will eventually be turned into the full 6.8 point release and ISO set, to the QA team today for testing.
I expect that it will take 1 to 2 days in QA and then those will be ready for release into the 6.7/cr/ repository. That means that no later than Monday, May 16th (and maybe as early as sometime within the next 24 hours), the CR packages, including the openssl update everyone is interested in, should be available. That is assuming we find no major issues requiring rebuilding during this testing.
I will also remind everyone that Red Hat gets 6 months of QA testing after a private beta release to get these out and correct any issues .. while the CentOS team only gets this Source Code on RHEL release day. That is when we can start building. We have to build major packages like gcc and glibc and kernel first as we want the latest of those in the other build roots. Then we have to build the new packages on which others depend on as a requires. Then we can build the other packages. There were 350 (ish) SRPMs that have produced about 3050 RPMs that all need to be vetted before release.
This process NORMALLY takes 10 days (when you get your first security udpates) for CR packages and 21 to 30 days for full tree release. It has been this way for 12 years, and it will be so i the future. If you can't wait 10 days to get the CentOS updates .. then buy RHEL.
If you have no idea what CR is .. ask and people can help you on the list. Here is the info in the wiki:
https://wiki.centos.org/AdditionalResources/Repositories/CR
Any if you are wondering why not earlier (though, 2 days is pretty fast if you ask me) ...this timebomb bug rendered both the openssl updates unbuildable:
https://bugzilla.redhat.com/show_bug.cgi?id=1335097
There where also a bugs where glutserfs, xmlgraphics-commons, and certmonger would not build.
The full release of the entire 6.8 tree and isos is still some time (10-20 days) away, but we should have CR packages soon.
Thanks, Johnny Hughes