public inbox for [email protected]
help / color / mirror / Atom feedFrom: Jeff Janes <[email protected]>
To: Bruce Momjian <[email protected]>
Cc: [email protected]
Subject: Re: 8.4 doc bug for "Incrementally Updated Backups"
Date: Sat, 24 Nov 2012 13:56:27 -0800
Message-ID: <CAMkU=1ysXB3GSz4FMRVSJcFfjPtuutktGLeFsmZ7A8o53yq2Aw@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAMkU=1xdumQ1FeBR=EJAeagjy1+76L9A5ALzE=Dk+yTA2DOs8Q@mail.gmail.com>
<[email protected]>
<CAMkU=1y3RveOPn_8c0X8ZTOeiD7A9dwP1GqUoKDU62V_s_zFXQ@mail.gmail.com>
<[email protected]>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-docs>
On Fri, Nov 23, 2012 at 5:36 PM, Bruce Momjian <[email protected]> wrote:
> On Fri, Nov 23, 2012 at 04:26:48PM -0800, Jeff Janes wrote:
>> On Fri, Nov 23, 2012 at 3:42 PM, Bruce Momjian <[email protected]> wrote:
>> >
>> > We don't assume people are reading docs from very old versions.
>> >
>>
>> Even if that is the version they are using? It is, after all, still
>> under maintenance,
>
> There are three options for doc patches:
>
> 1. patch only git head, meaning the next major release
> 2. do #1, plus the most recent major released version, e.g. 9.2.X
> 3. #1, #2, and all major supported released versions
>
> In general, #1 is normally for wording clarifications, #2 is for usage
> clarifications, and #3 is to correct mistakes. Not sure I follow that
> 100%, but that is what I normally do.
>
> Is that process good? Did I not follow it?
It was removed from 9.0 because it was considered to be unreliable. I
think that unreliable advice about taking backups is a mistake, so it
should have followed path #3. I guess it is also clarification, but a
pretty major one.
Cheers,
Jeff
--
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
view thread (10+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: 8.4 doc bug for "Incrementally Updated Backups"
In-Reply-To: <CAMkU=1ysXB3GSz4FMRVSJcFfjPtuutktGLeFsmZ7A8o53yq2Aw@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox