Subject: Re: [boost] Changes to VS 2012 config
From: Eric Niebler (eric_at_[hidden])
Date: 2012-11-29 13:49:50
On 11/29/2012 12:59 AM, Sebastian Redl wrote:
> On 29.11.2012 03:25, Eric Niebler wrote:
>> Herb has been pretty clear about this. The CTP releases are what we'll
>> get until the next major VS release, and the CTP releases are not
>> intended for production use. I see this as mostly Microsoft trying to
>> limit its liability. For Boost's purposes, I'd like to see us treat
>> the CTP releases as full-fledged toolsets. I don't expect the CTPs
>> will get bugfixes. We'll just get another CTP. But that's just a
>> guess; don't quote me.
> Haven't seen Herb's videos, but from the blog posts I've seen, that's
> not how it works.
> The CTPs are just that: community technical previews. In other words,
> pre-betas. Eventually (like Update 1 just did) they will become
> out-of-band releases. The VS2012 IDE will remain the same, but either
> the toolset is updated or you get a new selectable platform toolset.
> Update 1 added a new toolset. Update 2 (or whatever they'll call the
> variadics update) might not, if the compiled part of the runtime remains
> the same (or if MS simply doesn't care to give their users the choice).
> So we should treat the Updates as releases for Boost, but the CTPs are
> just betas. We can support them in the trunk, but if the final release
> of that Update has changes, don't expect Boost to support the CTP variant.
I'll be seeing Herb tomorrow. I'll ask him in person.
-- Eric Niebler BoostPro Computing http://www.boostpro.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk