Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Tcuyg-0007lk-L5 for pgsql-docs@arkaria.postgresql.org; Mon, 26 Nov 2012 09:27:46 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1Tcuyf-0000J0-C4 for pgsql-docs@arkaria.postgresql.org; Mon, 26 Nov 2012 09:27:45 +0000 Received: from makus.postgresql.org ([98.129.198.125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Tcuye-0000Iv-QU for pgsql-docs@postgresql.org; Mon, 26 Nov 2012 09:27:44 +0000 Received: from mail-la0-f46.google.com ([209.85.215.46]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Tcuyd-0007pK-3m for pgsql-docs@postgresql.org; Mon, 26 Nov 2012 09:27:44 +0000 Received: by mail-la0-f46.google.com with SMTP id p5so5594699lag.19 for ; Mon, 26 Nov 2012 01:27:42 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=zeh5dHow1KmP0bbVR4Z5vUWzbgl7J9SdaQLFaY5WhUk=; b=lrHhfajTUm6NKcEippIoAdd/+oZqpiWL0xFW3Dh7e9kPkYhxsIZTKcABi1JTuNDi4z dFYiGDPRpVeGTVmxKIPp1PQVm7Q0J88cJ5IBgnrPEHcJrksoCOF4NndLSkwM1eI7sqrC zkUaa3KPx2jWd4so2Q5zfy60k8jNLc55eN7kF3ekhqTJn1oUhbf2iLyiCv5bm3zpNjlv UKNQHe/9CwMa5xi1HF9EhYAX1VoBophdHp3NkKj/pm2jk9NHYWCydf/gE6DYL5y7nYf7 GoIkFbJxZETVVwzpOtzVBsWY1DLE8QQD1P9Twpiy/SrXf1tBCnoH/5WM52YBqL2vQilN 6qIA== MIME-Version: 1.0 Received: by 10.112.42.8 with SMTP id j8mr42938lbl.89.1353922061993; Mon, 26 Nov 2012 01:27:41 -0800 (PST) Received: by 10.152.20.233 with HTTP; Mon, 26 Nov 2012 01:27:41 -0800 (PST) In-Reply-To: References: <20121123234205.GA1605@momjian.us> <20121124013644.GA9382@momjian.us> Date: Mon, 26 Nov 2012 10:27:41 +0100 Message-ID: Subject: Re: 8.4 doc bug for "Incrementally Updated Backups" From: Magnus Hagander To: Jeff Janes Cc: Bruce Momjian , pgsql-docs Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkgt6vwzCTNK4ALykyuCVHcnDDTQWcCK4GqvCxO0qJpjGqijm0c3b+g5ChDMKT5xkDScnF6 X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org On Sat, Nov 24, 2012 at 10:56 PM, Jeff Janes wrote: > On Fri, Nov 23, 2012 at 5:36 PM, Bruce Momjian 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 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. I think it can be considered a bugfix, and thus correcting a mistake. But in generael, I think we may want to be a bit more aggressive in backpatching these things. First because people will likely read the docs for the version that they are using, and thus miss things. But possibly even more important, because we know that Google (and others) tend to link to older versions of the docs as search hits before the newer ones for quite a long time after a release (or forever in some cases), which makes it even more visible. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs