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

Ask for testing help for the option refactor branch. #14184

Merged
merged 1 commit into from
Jan 26, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions docs/markdown/snippets/optioncaution.md
Copy link
Member

@eli-schwartz eli-schwartz Jan 26, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you want to place this at the top of the release notes for extra visibility? Release notes are inserted in python sorted() order by filename. You can force something to the top in exceptional cases by prepending with 1-.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll fix that by hand when creating the final page.

Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
## Call for testing for next release

At the beginning of next cycle we aim to merge the [option refactor
branch](https://github.com/mesonbuild/meson/pull/13441). This is a
_huge_ change that will touch pretty much all code.

The main change it brings is that you can override any builtin option
value for any subproject (even the top one) entirely from the command
line. This means that you can, for example, enable optimizations on
all subprojects but not on the top level project.

We have done extensive testing and all our tests currently
pass. However it is expected that this will break some workflows. So
please test the branch when it lands and report issues. We want to fix
all regressions as soon as possible, preferably far before the next rc
release.
Loading