Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[c++] Dropping support for versions of Boost more than 2 years old #771

Open
chwarr opened this issue Jan 9, 2018 · 2 comments
Open

[c++] Dropping support for versions of Boost more than 2 years old #771

chwarr opened this issue Jan 9, 2018 · 2 comments

Comments

@chwarr
Copy link
Member

chwarr commented Jan 9, 2018

In preparation for adding CI testing for Boost 1.66 (release December 18, 2017), we're thinking about dropping support for versions of Boost older than 2 years. This would mean that we only test with Boost 1.61 and above instead of the current 1.58 and above.

Over time, as functionality only available in later versions of Boost is used, Bond would stop building with older versions of Boost.

Please add a comment to this issue with your thoughts and concerns.

@jasonzio
Copy link

Significant changes to Boost Test in 1.56 make Boost 1.55 really sticky.

@chwarr
Copy link
Member Author

chwarr commented Jan 10, 2018

Good point, @jasonzio. Thanks.

(And, we've had to do the Boost Test migration ourselves. :-))

One thing we're seeing in the opposite direction is the removal of things like std::auto_ptr from the standard library is pulling people up to Boost 1.65, the earliest version that excised its use of std::auto_ptr.

chwarr added a commit to chwarr/bond that referenced this issue Mar 23, 2018
Drops support for versions of Boost older than two years. Boost 1.61+ or
newer is now required. (Bond will likely continue to work with older
versions of Boost, but we'll no longer actively test against them.)

Using cron jobs, add coverage for all supported versions of Boost with
both Clang and G++.

This is the Travis-side fix for:
* microsoft#666
* microsoft#771
chwarr added a commit to chwarr/bond that referenced this issue Mar 23, 2018
Drops support for versions of Boost older than two years. Boost 1.61+ or
newer is now required. (Bond will likely continue to work with older
versions of Boost, but we'll no longer actively test against them.)

This is the AppVeyor-side fix for:
* microsoft#771
chwarr added a commit to chwarr/bond that referenced this issue Mar 23, 2018
Drops support for versions of Boost older than two years. Boost 1.61+ or
newer is now required. (Bond will likely continue to work with older
versions of Boost, but we'll no longer actively test against them.)

This is the AppVeyor-side fix for:
* microsoft#771
chwarr added a commit to chwarr/bond that referenced this issue Mar 29, 2018
This is part 1 of 2 in the process of dropping support for versions of
Boost older than two years. Boost 1.61+ or newer is now required. (Bond
will likely continue to work with older versions of Boost, but we'll no
longer actively test against them.)

We'd like to test with the current lowest version of Boost that Bond
supports, Boost 1.61. However, there is no Boost 1.61 available on
AppVeyor, so we start with the lowest version that is available in
AppVeyor and supported by Bond: 1.62.

This AppVeyor change needs to be made before the CMake minimum version
bump that we're planning to make with the Travis CI and README changes.

This is the AppVeyor-side change for
microsoft#771
ara-ayvazyan pushed a commit that referenced this issue Apr 6, 2018
Drops support for versions of Boost older than two years. Boost 1.61+ or
newer is now required. (Bond will likely continue to work with older
versions of Boost, but we'll no longer actively test against them.)

Using cron jobs, add coverage for all supported versions of Boost with
both Clang and G++.

This is the Travis-side fix for:
* #666
* #771
chwarr added a commit to chwarr/bond that referenced this issue Apr 18, 2018
The AppVeyor builder images contain some versions of Boost, but not all
the versions that Bond supports for all the compilers that it supports.

This commit:

* Adds a script to easily find the pre-installed Boost library.
* Adds a script to install a given version of Boost from NuGet.org
  packages.
* Updates the AppVeyor build to install missing versions of Boost from
  NuGet.org.
* Refactors the AppVeyor build to base the MSVC compiler off of the
  BOND_VS_VERSION or the APPVEYOR_BUILD_WORKER_IMAGE variable, which
  should set us up to add MSVC 2017 to the build later.

This is the AppVeyor side of microsoft#771
chwarr added a commit to chwarr/bond that referenced this issue Apr 18, 2018
The AppVeyor builder images contain some versions of Boost, but not all
the versions that Bond supports for all the compilers that it supports.

This commit:

* Switches to a minimum Boost of 1.61, the minimum supported version as
  of this commit.
* Adds a script to easily find the pre-installed Boost library.
* Adds a script to install a given version of Boost from NuGet.org
  packages.
* Updates the AppVeyor build to install missing versions of Boost from
  NuGet.org.
* Refactors the AppVeyor build to base the MSVC compiler off of the
  BOND_VS_VERSION or the APPVEYOR_BUILD_WORKER_IMAGE variable, which
  should set us up to add MSVC 2017 to the build later.

This is the AppVeyor side of microsoft#771
ara-ayvazyan pushed a commit that referenced this issue Apr 20, 2018
The AppVeyor builder images contain some versions of Boost, but not all
the versions that Bond supports for all the compilers that it supports.

This commit:

* Switches to a minimum Boost of 1.61, the minimum supported version as
  of this commit.
* Adds a script to easily find the pre-installed Boost library.
* Adds a script to install a given version of Boost from NuGet.org
  packages.
* Updates the AppVeyor build to install missing versions of Boost from
  NuGet.org.
* Refactors the AppVeyor build to base the MSVC compiler off of the
  `BOND_VS_VERSION` or the `APPVEYOR_BUILD_WORKER_IMAGE` variable, which
  should set us up to add MSVC 2017 to the build later.

This is the AppVeyor side of #771
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants