-
Notifications
You must be signed in to change notification settings - Fork 164
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
Prepare for release with Boost 1.80 #667
Comments
Includes changes up to commit 25 from the table shown in <boostorg#667>.
Includes changes up to commit 25 from the table shown in <#667>.
Includes changes up to commit 106 (hash 36a45e3) from the table shown in <boostorg#667>. Those are all commits form the grand merge. [ci skip]
Includes changes up to commit 106 (hash 36a45e3) from the table shown in <boostorg#667>. Those are all commits form the grand merge. [ci skip]
I've just pushed another merge from develop to master in b1d64ab |
I've just pushed /cc @marco-langer |
Changes on the documentation are still possible until 6th of July according to the Boost 1.80 release schedule. Does this also include PRs on the examples? (IMO: yes, examples are part of the documentation) |
Yes, of course. Documentation, examples, tests and stuff inside I've been rushing with merging PRs but postponed updates to |
I've just pushed, I think, the last major changes We are free to make changes to docs, examples, tests, and other non-breaking changes. |
Here is likely the final batch of changes to collect release notes for:
|
I think we are good now and on time before the Boost super-project |
Now might be a good time to do that. The Boost 1.80.0 beta 1 has been released last week and the release notes are up on the website, but they show no changes for GIL - so far. Considering that GIL in Boost 1.80.0 brings a lot of changes - among them a breaking by switching to C++14 - those changes should be made visible on the website. As far as I understand somebody has to create a PR on the website repository to update those notes, so I took the liberty to do that: boostorg/website#696 Somebody (@mloskot?) should still check the syntax, though, because that's the first time I have written something in QuickBook format. |
@striezel Yes, I meant to do it sooner but I've got swamped with other stuff. So, thank you for the golden helping hand with the PR. I will check it. UPDATE: Done, boostorg/website#696 merged. |
We're done here. Congratulations and thanks to every one involved! |
Following the #663 discussion, we are going to perform the grand true merge of
develop
intomaster
in order to prepare for release all of the fixes and features (GSoC too) that have been developed over the Boost 1.76.0, that is the last Boost release with anything GIL.Steps:
git push
RELEASES.md
Changes
Below is initial, as on 12 May 2022, log of commits in form convenient to review that will merged from current develop into master for release with Boost 1.80:
git log origin/master..develop --reverse --pretty=format:" | %cs | [%h](http://github.com/boostorg/gil/commit/%H) | %s |" | nl | sed -E 's/^\s/\|/g'
Merge
Build (local)
On Windows, using VS 2022,
core
only:b2.exe cxxstd=11 variant=release address-model=64 libs/gil/test/core
On Linux, using gcc 10, all default tests
./b2 cxxstd=11 variant=release address-model=64 libs/gil/test
All pass.
The text was updated successfully, but these errors were encountered: