From: Niall Douglas (s_sourceforge_at_[hidden])
Date: 2021-10-27 12:21:15
On 27/10/2021 03:10, Gavin Lambert via Boost wrote:
> On 26/10/2021 08:22, Peter Dimov wrote:
>> The Visual Studio 2022 (msvc-14.3) release date is Nov 8, which is
>> right in
>> the middle of our beta master freeze (Nov 3 - Nov 10). Since VS2022 is
>> now RC2, which means that it won't change much if at all, we probably
>> need to start testing our libraries with it now, so that the issues
>> are ironed
>> out before 1.78 beta.
>
> This is not the first time that an MSVC release has conflicted with
> Boost's release schedule -- it seems likely that Microsoft's release
> date targets were chosen with similar logic to Boost's.
>
> Would it make sense to permanently shift the Boost calendar target to
> reduce the risk of future such conflicts?
A major release of MSVC only happens every few years. Most of the
userbase won't touch a new major MSVC release for a year in any case. Me
personally, I'm very relaxed about supporting new major MSVC releases
immediately, everybody can afford to wait until three months or so
following a MSVC major release.
Now, it has been in the past that Boost didn't work right on a new major
MSVC release for a year afterwards. I remember sending in patches and
hassling people to up their game on that. But that was a long time ago
now, and back when Boost wasn't as vibrant as it is today.
Niall