Skip to content

Commit bb428cb

Browse files
tglsfdctglsfdc
committed
Doc: in each release branch, keep only that branch's own release notes.
Historically we've had each release branch include all prior branches' notes, including minor-release changes, back to the beginning of the project. That's basically an O(N^2) proposition, and it was starting to catch up with us: as of HEAD the back-branch release notes alone accounted for nearly 30% of the documentation. While there's certainly some value in easy access to back-branch notes, this is getting out of hand. Hence, switch over to the rule that each branch contains only its own release notes. So as to not make older notes too hard to find, each branch will provide URLs for the immediately preceding branches' release notes on the project website. There might be value in providing aggregated notes across all branches somewhere on the website, but that's a task for another day. Discussion: https://postgr.es/m/cbd4aeb5-2d9c-8b84-e968-9e09393d4c83@postgresql.org
1 parent 2f93b74 commit bb428cb

13 files changed

+74
-97482
lines changed

‎doc/src/sgml/filelist.sgml

Lines changed: 0 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -165,17 +165,6 @@
165165

166166
<!ENTITY release SYSTEM "release.sgml">
167167
<!ENTITY release-9.4 SYSTEM "release-9.4.sgml">
168-
<!ENTITY release-9.3 SYSTEM "release-9.3.sgml">
169-
<!ENTITY release-9.2 SYSTEM "release-9.2.sgml">
170-
<!ENTITY release-9.1 SYSTEM "release-9.1.sgml">
171-
<!ENTITY release-9.0 SYSTEM "release-9.0.sgml">
172-
<!ENTITY release-8.4 SYSTEM "release-8.4.sgml">
173-
<!ENTITY release-8.3 SYSTEM "release-8.3.sgml">
174-
<!ENTITY release-8.2 SYSTEM "release-8.2.sgml">
175-
<!ENTITY release-8.1 SYSTEM "release-8.1.sgml">
176-
<!ENTITY release-8.0 SYSTEM "release-8.0.sgml">
177-
<!ENTITY release-7.4 SYSTEM "release-7.4.sgml">
178-
<!ENTITY release-old SYSTEM "release-old.sgml">
179168

180169
<!ENTITY acronyms SYSTEM "acronyms.sgml">
181170

0 commit comments

Comments
 (0)