Subject: Re: [boost] [release] Boost 1.66.0 Release Candidate 2
From: Peter Dimov (lists_at_[hidden])
Date: 2017-12-15 12:18:01
Daniel James wrote:
> > I agree that this message isn't going to make us many new friends, and
> > that it doesn't provide much value in this specific case.
> We don't have testers for the new version of Visual Studio yet, so the
> warning message is entirely correct. Silencing it would do no favours to
> anyone who relies on it.
Nobody relies on it, and it's not actionable. The only thing you can
possibly do is silence it, and the only thing you would do is silence it.
Note that this is not a general statement. It's about this specific case.
> If you want to discuss this, I'd suggest starting a new thread, and
> putting '[config]' in the subject, so that it will get the attention of
> the appropriate people.
The appropriate people have already applied the necessary changes to Config,
and those changes are (correctly) not going into the release. There's
nothing the appropriate people need to do.
> Release managers shouldn't force a change on a library that's working as
> intended, unless it's causing failures.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk