$include_dir="/home/hyper-archives/boost/include"; include("$include_dir/msg-header.inc") ?>
Subject: Re: [boost] [test] Applying outstanding pull requests to develop and schedule merge of develop to master
From: Gennadiy Rozental (rogeeff_at_[hidden])
Date: 2014-12-26 05:17:06
Brian Schrom <brian.schrom <at> pnnl.gov> writes:
>
> 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.
Isn't this what Modular Boost is all about? Boost.Test master is latest
release everybody depends on. Boost.Test devel is where new features are
developed.
Gennadiy