model-writtenrun 9720 - may be wrong, links go to the source messages. Commit-by-commit LLM analysis is in the Commits dialog.
- Tom Lane proposed removing release notes for branches already unsupported when a release shipped, citing documentation build time, download size and the risk of exceeding TeX limits #1.
- Jonathan S. Katz proposed a website archive, while Tom emphasized avoiding duplicate manual maintenance and preserving recoverability; Jonathan explained that archived tarballs could supply the historical content #3 #9 #14 #15.
- Jonathan posted a working pgweb prototype that extracted release notes during documentation loading and displayed them from a separate table, but navigation, cross-reference handling, version metadata and dependency review remained unfinished #17.
- Bruce Momjian suggested retaining the old SGML files without building them, but Tom opposed the tarball overhead and continued edits to historical material #20 #21.
- Peter Eisentraut proposed keeping only each major version's own release notes; Bruce raised the need to consult intervening releases during upgrades and requested a downloadable collection of historical notes #22 #24.
- Magnus Hagander questioned the prototype's duplicate storage and proposed an index linking to release notes already hosted in their original version's documentation, which would also avoid rewriting links #27.
- After several months, Jonathan revived the per-branch approach with links to older branches, and Tom and Bruce agreed that applying it to supported back branches would avoid maintaining conflicting workflows #28 #30 #31.
- Jonathan and Tom initially judged redirects unnecessary given low historical-page traffic, accepting that removing duplicated pages would produce broken URLs #32 #33 #34.
- Tom posted the documentation-trimming patch, explicitly omitting the planned obsolete-file deletions from its attachment, and measured roughly 20% faster HTML builds and substantially smaller documentation output #35.
- Jonathan reviewed the patch's syntax and maintenance instructions; Tom then clarified that prior-release links would describe support at the time of release, avoiding ongoing retirement updates in released branches or links to future versions #36 #37 #39.
- Tom committed the trimming patch with revised wording, the announced file deletions, release-process instructions and a placeholder cleanup as 527b5ed1ad, applying the policy to supported branches; subsequent tarball builds showed approximately 6–7% compressed-size savings #41.
- After the commit, Andres Freund and Alvaro Herrera objected to removing supported branches' notes, citing harder historical searches, upgrade research and broken existing links; Jonathan offered to revisit redirects and the archive prototype #42 #43 #44 #46 #49 #50.
- Tom identified a further problem: draft minor-release notes now lived on branches without automatic website publication, and proposed a separate aggregate-notes repository that could publish drafts independently #47 #48.
- Discussion exposed the need for aggregated notes to link to the correct version's documentation; Jonathan offered website work and an alternative using existing stored pages, while Tom ended by favoring a single authoritative source per release with aggregation through links or redirects #54 #55 #56 #58.
- The trimming commit remained in place at the thread's end, with no revert or additional patch posted; the pgweb prototype, aggregation mechanism, redirects and draft-publication solution remained unresolved #58.