On 31/07/2017 15:04, Thomas Heller via Boost wrote:
On 07/31/2017 02:23 PM, Niall Douglas via Boost wrote:
[...] and the "Boostification" cronjob script as the peer review wants a "pure Boost" submission.
Where would one find the script and the result of the boostified headers?
As the announcement said, the boostification script has not been implemented. Nor will it be until the documentation and tutorial are finished for obvious reasons. That's some months away yet, probably November or December, after the Meeting C++ conference and the Albuquerque WG21 meeting. The implementation code however is ready to go, and works very well with Boost code as it's exactly like a STL vocabulary type. If you can meet the steep compiler version requirements of course.
What's the rationale in having it run as a cronjob instead of having the CI do the boostification upon a successful build?
Outcome runs on both Travis and Appveyor. Each cannot know if the other succeeded. So a cronjob which already exists scans nightly the CDash for Outcome, and figures out the last commit with all tests passing on all platforms. It then updates master branch to that commit, and publishes a tarball. That same cronjob will eventually also Boostify Outcome into the Boost.Outcome repo if and only if all tests pass i.e. master branch got updated. Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/