On 11/15/20 9:00 AM, David G. Johnston wrote:
On Sun, Nov 15, 2020 at 9:39 AM Adrian Klaver <adrian.klaver@xxxxxxxxxxx
<mailto:adrian.klaver@xxxxxxxxxxx>> wrote:
On 11/14/20 8:24 PM, David G. Johnston wrote:
> On Fri, Nov 13, 2020 at 1:48 PM Adrian Klaver
<adrian.klaver@xxxxxxxxxxx <mailto:adrian.klaver@xxxxxxxxxxx>
> <mailto:adrian.klaver@xxxxxxxxxxx
<mailto:adrian.klaver@xxxxxxxxxxx>>> wrote:
>
> Which is an indication that for changes of this scope it would be
> prudent to create a mock up and have end users see and comment on
> before
> rolling them out.
>
>
> There were mockups and people did provide comments. Do you have any
Where were they announced and when?
Starting back in February.
https://www.postgresql.org/message-id/9326.1581457869@xxxxxxxxxxxxx
<https://www.postgresql.org/message-id/9326.1581457869@xxxxxxxxxxxxx>
The first commit was applied in April.
> concrete suggestions on what should have been done, or done
differently?
Yes my concrete suggestion was a return to previous layout.
I am referring to the process by which the idea to change the
documentation layout was made public so people could review it (see above).
In hindsight it could have been handled better. Waiting longer at
different points and making pronouncements on -announce to solicit
feedback from people who don't follow -docs. That doesn't change the
Yes and at least one post to --general. It would have motivated me to
look at the new docs earlier.
fact that we need to move forward with a new patch to "fix" things. If
the agreement is that fix looks a lot like the old format then so be
it. But getting there by reverting doesn't seem doable.
The method does not matter to me the layout does.
David J.
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx
