boostorg
Prepare for release with Boost 1.86
Seeing that the last Boost release with changes in GIL was Boost 1.80.0 in August 2022 and seeing that some fixes and features have landed on the develop branch during that time, it is probably a good time to perform the next true merge of develop into master to prepare for the next release of GIL / Boost.
Steps:
- [ ] Merge (@mloskot?)
- [ ] Build locally before
git push(optional, because the CI should catch any errors) - [ ] Push
- [ ] Review CI status
- [ ] Collect release notes to
RELEASES.md(see #749) - [ ] Copy release notes to https://github.com/boostorg/website/
Changes
Below is an initial log of commits that will get merged from current develop into master for release with Boost 1.86 (as of 30 June 2024):
git log origin/master..develop --reverse --pretty=format:" | %cs | [%h](http://github.com/boostorg/gil/commit/%H) | %s |" | nl | sed -E 's/^\s/\|/g'
| # | Date | Hash | Subject |
|---|---|---|---|
| 1 | 2022-08-10 | 8465d5463 | ci: partially replace Ubuntu 18.04 on GHA with Ubuntu 20.04 (#716) |
| 2 | 2022-08-12 | 1f89d622e | ci: replace macOS 10.15 with macOS 11 in CI pipelines (#717) |
| 3 | 2022-10-05 | 135edcfad | docs: Support newer version of Sphinx (#719) |
| 4 | 2022-10-06 | 3f7daa99b | docs: Fix HTML syntax |
| 5 | 2022-11-14 | 1df8c2407 | ci: Update actions/checkout in GitHub Actions workflows to v3 (#720) |
| 6 | 2023-02-07 | 712b827ed | fix: Convolution in convolve_2d (#723) |
| 7 | 2023-02-07 | d6e67f38c | fix: Normalize Gaussian 2D kernel. (#725) |
| 8 | 2023-02-21 | 8f4cdcbcc | fix: Fixed custom color converter in dynamic_factory and added corresponding (#726) |
| 9 | 2023-02-22 | ecea33a90 | fix: Make locator.hpp self contained (#729) |
| 10 | 2023-03-16 | eabd679f6 | fix: Documentation (#731) |
| 11 | 2023-10-01 | e24c87fde | ci: ubuntu-18.04 environment is deprecated (#738) |
| 12 | 2023-12-25 | 3a4d45443 | ci: update actions/checkout in GitHub Actions workflows to v4 (#739) |
| 13 | 2023-12-25 | 822c19ee7 | ci: fix Python package in coverage workflow (#740) |
| 14 | 2024-01-27 | 322c4e2e1 | Updated Boost.Filesystem usage. (#741) |
| 15 | 2024-04-18 | 2c3ee866b | Portable minmax Win32-API workaround #744 (#745) |
| 16 | 2024-05-10 | 4fec872fe | feat: Guard boost::filesystem usage (#743) |
| 17 | 2024-05-13 | abb561a22 | fix: Wrong buffer size in path string conversion functions (#746) |
| 18 | 2024-05-17 | 481b6e7c1 | feat: add tell() and error() functions to istream + ostream devices (#747) |
(If this looks familiar, then because it was shamelessly copied from #667, the issue for the Boost 1.80 release.)
Timeline
According to the calender on https://www.boost.org/community/index.html the following dates are relevant for the release:
| Date | Subject | Description |
|---|---|---|
| 2024-06-24 | Boost 1.86.0 closed for new libraries and breaking changes | Release branch is closed for new libraries and breaking changes to existing libraries. Still open for bug fixes and other routine changes to all libraries without release manager review. |
| 2024-07-03 | Boost 1.86.0 closed for major changes | Release closed for major code changes. Still open for serious problem fixes and docs changes without release manager review. |
| 2024-07-10 | Boost 1.86.0 closed for beta | Release closed for all changes |
| 2024-07-17 | Boost 1.86.0 beta | Beta posted for download. |
| 2024-07-18 | Boost 1.86.0 open for bug fixes | Release open for bug fixes and documentation updates. Other changes by permission of a release manager. |
| 2024-08-07 | Boost 1.86.0 closed | Release closed for all changes |
| 2024-08-14 | Boost 1.86.0 release | Release posted for download. |
We are already past the first date in that list, but a first glance at the commit list above shows no obvious breaking changes, so it probably is still fine. There are still a few days left before the beta is closed for major changes, so we should still be able to get the changes from develop in right in time before the beta.
