From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
---|---|
To: | Kirk Wolak <wolakk(at)gmail(dot)com> |
Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: February 9th, 2023 Release links to a missing page |
Date: | 2023-02-21 14:50:04 |
Message-ID: | 8b27c72e-e3cd-972d-0cfb-7aae8c359b8e@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On 2/20/23 8:57 PM, Kirk Wolak wrote:
> On Sun, Feb 19, 2023 at 4:55 PM Jonathan S. Katz <jkatz(at)postgresql(dot)org
> Well, that gives me an idea. In the release announcement, we could
> put a
> line that says "You can send any corrections or suggestions to the
> public pgsql-www(at)lists(dot)postgresql(dot)org
> <mailto:pgsql-www(at)lists(dot)postgresql(dot)org> mailing list" or something like
> that. That way, it would remove the guessing on what to do.
>
> Perfect... I love this community!
Thanks. As I'd probably forget before the next update announcement, I
sketched out the draft of it to ensure it included a line[1] around how
to report corrections/suggestions.
Thanks again!
Jonathan
From | Date | Subject | |
---|---|---|---|
Next Message | PG Doc comments form | 2023-02-21 15:14:17 | MERGE examples not clear |
Previous Message | Laurenz Albe | 2023-02-21 09:51:42 | Re: Transaction wraparound and read committed isolation level |