Subject: Re: [boost] Travis CI Resources
From: Peter Dimov (lists_at_[hidden])
Date: 2018-01-22 16:14:38
Andrey Semashev wrote:
> > That said, you're quite correct that working from a fork is a superior
> > workflow.
> It's inconvenient though.
It's pretty inconvenient as making a Boost library work out-of-superproject
can be a bit of a challenge, and switching the in-superproject directory to
the fork has its downsides too.
On the other hand though, Travis turnaround improves drastically as you're
back to 5 jobs and don't wait for anyone else, and people can no longer
blame you for their boostorg jobs being stuck. So it seems worth looking
All that said, we (boostorg) could really use 10 jobs, and whatever better
Mac support money can buy.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk