forked frompostgres/postgres
- Notifications
You must be signed in to change notification settings - Fork6
Commit60b1d6c
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 theproject. That's basically an O(N^2) proposition, and it was starting tocatch up with us: as of HEAD the back-branch release notes alone accountedfor nearly 30% of the documentation. While there's certainly some valuein easy access to back-branch notes, this is getting out of hand.Hence, switch over to the rule that each branch contains only its ownrelease notes. So as to not make older notes too hard to find, eachbranch will provide URLs for the immediately preceding branches'release notes on the project website.There might be value in providing aggregated notes across all branchessomewhere on the website, but that's a task for another day.Discussion:https://postgr.es/m/cbd4aeb5-2d9c-8b84-e968-9e09393d4c83@postgresql.org1 parent16e0464 commit60b1d6c
File tree
15 files changed
+74
-121835
lines changed- doc/src/sgml
15 files changed
+74
-121835
lines changedLines changed: 0 additions & 13 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
169 | 169 | | |
170 | 170 | | |
171 | 171 | | |
172 | | - | |
173 | | - | |
174 | | - | |
175 | | - | |
176 | | - | |
177 | | - | |
178 | | - | |
179 | | - | |
180 | | - | |
181 | | - | |
182 | | - | |
183 | | - | |
184 | | - | |
185 | 172 | | |
186 | 173 | | |
187 | 174 | | |
| |||
0 commit comments
Comments
(0)