Received: from malur.postgresql.org ([2a02:16a8:dc51::56])
	by arkaria.postgresql.org with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <pgsql-pkg-debian-owner+archive@lists.postgresql.org>)
	id 1fHA68-0000Kz-VQ
	for pgsql-pkg-debian@arkaria.postgresql.org; Fri, 11 May 2018 15:36:45 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-pkg-debian-owner+archive@lists.postgresql.org>)
	id 1fHA67-00025m-2s
	for pgsql-pkg-debian@arkaria.postgresql.org; Fri, 11 May 2018 15:36:43 +0000
Received: from makus.postgresql.org ([2001:4800:1501:1::229])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <l.mantrova@postgrespro.ru>)
	id 1fHA66-00025Z-HX; Fri, 11 May 2018 15:36:42 +0000
Received: from mail.postgrespro.ru ([93.174.131.138])
	by makus.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <l.mantrova@postgrespro.ru>)
	id 1fHA62-0001ak-T9; Fri, 11 May 2018 15:36:41 +0000
Received: from localhost (localhost [127.0.0.1])
	by mail.postgrespro.ru (Postfix) with ESMTP id 183B321C1F69;
	Fri, 11 May 2018 18:36:36 +0300 (MSK)
X-Virus-Scanned: Debian amavisd-new at postgrespro.ru
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=x tagged_above=-99 required=4 WHITELISTED tests=[]
	autolearn=unavailable
Received: from [192.168.27.124] (gw.postgrespro.ru [93.174.131.141])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(Client did not present a certificate)
	by mail.postgrespro.ru (Postfix) with ESMTPSA id DE59621C1F68;
	Fri, 11 May 2018 18:36:35 +0300 (MSK)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru;
	s=mail; t=1526052995;
	bh=6Kt9l9ZpSDpW6nLczGj5yPSIW+MaC56FSVK9jAYa0kE=;
	h=From:Subject:To:Date;
	b=Krm/YVLE0RH8BFU1ox3CJp9HwE5j4QQ4A706UBLPdgMfQYFnAYbtwZ9lqxly/B+yf
	 Ra46vV0AouojrDZq0xz13gfqCkMUu5iqwoBzyapj8TtMaLNDf8Io5+/GIcNEBMawFR
	 JI28vSPLhVmRCBteXkbsCo5gQPWxwGn1XJZjREHo=
From: Liudmila Mantrova <l.mantrova@postgrespro.ru>
Subject: Backporting XML docs
To: pgsql-pkg-debian@postgresql.org, pgsql-pkg-yum@postgresql.org
Message-ID: <06efc906-16f8-0cde-5bee-e3d5abfc00ba@postgrespro.ru>
Date: Fri, 11 May 2018 18:36:35 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.7.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
List-Id: <pgsql-pkg-debian.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-pkg-debian@lists.postgresql.org>
List-Owner: <mailto:pgsql-pkg-debian-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-pkg-debian>
Precedence: bulk

Dear all,

As you know, documentation for PostgreSQL 11 is now converted to XML. To 
avoid the overhead of adapting each patch that needs to be backported to 
be a valid SGML, hackers have been recently discussing the possibility 
of switching to XML in all supported branches.

Should this move happen, do you anticipate any packaging issues in older 
branches?
As far as I understand, branch 10 is already using the same toolchain as 
branch 11, even though with SGML sources.

-- 
Liudmila Mantrova
Technical writer at Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company