model-writtenrun 3109 - may be wrong, links go to the source messages. Commit-by-commit LLM analysis is in the Commits dialog.
- Peter Eisentraut opened the discussion by proposing that Meson cease being described as experimental for Windows builds using Visual Studio, while retaining that qualification elsewhere, because Meson had become the only supported route for those Windows builds #1.
- Aleksander Alekseev supplied the Visual Studio product name, identified the confusing section title, and raised the missing minimum Ninja version before submitting separate Meson-status and section-renaming patches #2 #3.
- Andrew Dunstan reported a failed Visual Studio backend build and advocated Ninja; Aleksander suggested removing the backend option from the documentation, but Andres Freund argued that the Visual Studio backend should work and should be fixed for developers who use it #4 #5 #6.
- Robert Haas questioned whether Meson still deserved the experimental label, while Dave Page argued that Windows support was less mature than Linux support based on his recent testing #8 #9.
- Peter defended retaining caution on other platforms because of missing configure/make features and insufficient verification of extensions against Meson-generated PGXS; Robert acknowledged those concerns #11 #12.
- Following Heikki Linnakangas's request for details, Dave identified zlib detection awaiting a fix, uuid detection already fixed by Andrew, and a GSSAPI/OpenSSL failure that also affected the older build system #10 #13.
- Noah Misch committed the Visual Studio rename from #3 as 3cffe7946c, adding matching section-identifier changes and backpatching to PostgreSQL 17, while explicitly leaving the Meson patch unexamined #14.
- Aleksander resubmitted the unchanged remaining Meson patch for CommitFest tracking #15; Noah subsequently corrected an additional platform-notes sentence's Visual Studio and Meson names in e56ccc8e42, which was not present in either attachment.
- Peter ultimately committed the remaining patch from #15 with only whitespace changes as 5afaba6297 and announced completion in #16, leaving both submitted changes landed while the Ninja-version and Visual Studio backend questions received no documented resolution in this thread.