On 11/11/16 23:16, Andrey Semashev wrote:
On 11/11/16 23:00, Rene Rivera wrote:
One obvious one.. What would happen when someone checks out and old version and the testing infrastructure has change enough that the old version doesn't work any longer?
Same thing when he does that with libraries - it would probably not work.
Do we ignore that possibility and fail in some unpredictable way? Do we implement some version checking and fail nicely but prevent "users" from running the scripts? Do we want to support backward version testing of testing infrastructure to ensure the version checking works for all possible past versions against future versions?
That is up to you, the maintainers of the testing infrastructure. As far as I'm concerned, it can fail horribly.
My point is that there should be a reliable way to checkout any Boost release,
I should have said "any Boost version" here, not just release. Potentially, any revision. And it should work the same way it worked when it was tested.