I know this comes up frequently, and its been a long time coming... I'd like to get a process in places that takes advantage of CI.
The GitHub/Travis-CI combination appears to have some gaps (https://github.com/travis-ci/travis-ci/issues/1724), so we have to be careful about what we do. I'm not trying to throw the baby out with the bath water, but we do need to ensure a Travis compromise does not lead to a Crypto++ compromise. We are tracking things with "Issue 92: Continuous integration and testing", http://github.com/weidai11/cryptopp/issues/97. -- -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com. --- You received this message because you are subscribed to the Google Groups "Crypto++ Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
