Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1f1wzM-0000DL-LO for pgsql-docs@arkaria.postgresql.org; Fri, 30 Mar 2018 16:34:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1f1wzL-0003BV-61 for pgsql-docs@arkaria.postgresql.org; Fri, 30 Mar 2018 16:34:51 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1f1wzL-0003BM-0K for pgsql-docs@lists.postgresql.org; Fri, 30 Mar 2018 16:34:51 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1f1wzH-0002zY-El for pgsql-docs@lists.postgresql.org; Fri, 30 Mar 2018 16:34:50 +0000 Received: from bruce by momjian.us with local (Exim 4.84_2) (envelope-from ) id 1f1wzE-0006er-Tn; Fri, 30 Mar 2018 12:34:44 -0400 Date: Fri, 30 Mar 2018 12:34:44 -0400 From: Bruce Momjian To: Magnus Hagander Cc: Euler Taveira , scott.ure@caseware.com, pgsql-docs@lists.postgresql.org Subject: Re: Documentation for varbit is missing size parameter Message-ID: <20180330163444.GN8476@momjian.us> References: <152074343671.1853.18284519607571497106@wrigleys.postgresql.org> <20180330151828.GL8476@momjian.us> <20180330162604.GM8476@momjian.us> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Fri, Mar 30, 2018 at 06:28:15PM +0200, Magnus Hagander wrote: > On Fri, Mar 30, 2018 at 6:26 PM, Bruce Momjian wrote: > Uh, I am always debating how important it is to backpatck vs the churn > we require of translations of our docs.  In this case, it didn't seem > worthwhile to have all of those translations try to deal with this > change for all those back branches. > If it's a clean backpatch I'd say it is -- people who are using PostgreSQL 9.6 > will be reading the documentation for 9.6 etc, so they will not know about the > fix then. > > If it's not a clean backpatch I can certainly see considering it, but if it's > not a lot of effort then I'd say it's definitely worth it. > > I really don't think considerations for translators of the *docs* are an issue > here. If you don't backpatch it, then nobody gets the fix. If you backpatch it, > then English readers do get the fix, and translated docs readers *might* get > the fix, depending on how they are maintained. It's not like translatable > strings where if they change in a backbranch they will revert to English unless > the translation is updated -- for the docs, they just don't get the fix.  My logic is that the more we backpatch, the less likely translators are going to be to keep their docs up-to-date with minor releases since the minor release diff is larger and contains more items that aren't _required_ for correctness. I looked at this patch and thought it was more a stylistic item rather than a correction. Is that right? -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +