Re: [boost] [Git] Documentation for Git and Modular Boost conversion

Subject: Re: [boost] [Git] Documentation for Git and Modular Boost conversion
From: Julian Gonggrijp (j.gonggrijp_at_[hidden])
Date: 2012-12-17 13:43:58

Dave Abrahams wrote:

> on Sun Dec 16 2012, "Peter Dimov" wrote:
> 
>> I wonder how testing will work. Will the "develop" and "master"
>> branches of each repo be tested? 
> 
> What's going to be tested is fluid.  The ultimate goal is to allow
> developers to request specific combinations of tests with each commit by
> modifying a .json file in their project's root directory.  In the
> meantime, I expect to test every commit on any branch.

Wouldn't the latter be a giant amount of work for the testers?

I do subscribe to the idea that testing should be configurable by the 
developers. I'm not sure whether a file that is subject to version 
control would be a wise way to provide for that configurability.

Not all testing should be optional, I think; form my understanding of 
the purpose of the test infrastructure it seems that the temporary 
release branches (gitflow style) should always be tested.

> The biggest question is against which versions of Boost dependencies the
> commit will be tested.  The obvious choices are 1. the version that was
> part of the last boost release, and 2. the last version of the
> dependency to be individually released (i.e. that dependency's "master"
> branch).
> 
> Feedback/opinions on that choice are most welcome.

Definitely option 2, conflicts are likely to be found sooner in that 
way.

-Julian