11 Dec
2014
11 Dec
'14
6 p.m.
On 12/11/2014 04:28 PM, Jamie Allsop wrote:
To recap - it is time to start actively shepherding patches into Boost.Test develop, but more importantly, it is time we started looking at a schedule for merging Boost.Test develop to master. The longer it is left the worse the impact will be. A lot of good work has been done on develop - the longer it stays there the more people will move away from Boost.Test in their own code and it will only have relevance to Boost libraries themselves.
Jamie
I really think that boost test needs to be it's own product (and development cycle) and that Boost references a released binary of it.