Re: Release note trimming: another modest proposal
| От | Andres Freund |
|---|---|
| Тема | Re: Release note trimming: another modest proposal |
| Дата | |
| Msg-id | 20190205060201.jo3ejddklqxb5a4q@alap3.anarazel.de обсуждение исходный текст |
| Ответ на | Re: Release note trimming: another modest proposal (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Release note trimming: another modest proposal
Re: Release note trimming: another modest proposal Re: Release note trimming: another modest proposal |
| Список | pgsql-docs |
Hi, On 2019-01-26 10:06:06 -0500, Tom Lane wrote: > "Jonathan S. Katz" <jkatz@postgresql.org> writes: > > The one "caveat" I will bring up is that once pushed and applied to the > > site, we would bring introduce a lot of 404s into the website. > > Hm. In principle we could probably insert some redirects, but > I doubt it's worth the trouble. > > If I haven't heard objections, I'll see about making this happen > during the first week of Feb (after the CF closes, but before > it's time to do the February releases' notes). Gah, I'd skipped this thread, because I was OK, if not happy, about the original modest proposal (trimming to supported versions). My fault. For the record: I think this is a terrible idea. Makes it much harder to figure out what changed when, and requires per-branch incantations to grep through the log. That's not to speak of the fact that now it's just about impossible to reference all releasenotes on the website in a useful manner now. For crying out loud, super prominent and often referenced URLs like https://www.postgresql.org/docs/devel/release-10.html are now broken, and soon URLs like https://www.postgresql.org/docs/current/release-10.html will be too. I don't understand how this can be considered a good idea. Greetings, Andres Freund
В списке pgsql-docs по дате отправления: