Re: Release note bloat is getting out of hand

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Mon, Feb 2, 2015 at 3:11 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> So I'm bemused by Robert's insistence that he wants that format to support
>> searches. As I said, I find it far more convenient to search the output
>> of "git log" and/or src/tools/git_changelog --- I keep text files of those
>> around for exactly that purpose.

> I normally search in one of two ways. Sometimes a grep the sgml;
> other times, I go to, say,
> http://www.postgresql.org/docs/devel/static/release-9-4.html and then
> edit the URL to take me back to 9.3, 9.2, 9.1, etc. It's true that
> 'git log' is often the place to go searching for stuff, but there are
> times when it's easier to find out what release introduced a feature
> by looking at the release notes, and it's certainly more useful if you
> want to send a link to someone who is not git-aware illustrating the
> results of your search.

> Well, maybe I'm the only one who is doing this and it's not worth
> worrying about it just for me. But I do it, all the same.

I'm not out to take away a feature you need. I'm just wondering why it
has to be supported in exactly the way it's done now. Wouldn't a
separately maintained release-notes-only document serve the purpose fine?

regards, tom lane