Date: Mon, 26 Sep 2022 22:25:09 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>,
	=?utf-8?Q?J=C3=BCrgen?= Purtz <juergen@purtz.de>,
	pgsql-docs@lists.postgresql.org
Subject: Re: DocBook 5.2
Message-ID: <YzJfBb+79/gW0d5y@momjian.us>
References: <ae14eca5-f57c-2db2-42ce-258bab3c6806@purtz.de>
 <20220905111508.wzgmpbcarxizdnin@alvherre.pgsql>
 <YzIY/OCgljTdqOgX@momjian.us>
 <3524032.1664228552@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <3524032.1664228552@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/YzJfBb%2B79/gW0d5y%40momjian.us>
Precedence: bulk

On Mon, Sep 26, 2022 at 05:42:32PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > On Mon, Sep  5, 2022 at 01:15:08PM +0200, Álvaro Herrera wrote:
> >> OK, these seem quite significant changes that are likely to cause great
> >> pain.  So I repeat my question, what are the benefits of making this
> >> change?  They better be very very substantial.
> 
> > Would we be converting docs for all supported versions of Postgres to
> > use DocBook 5.2, or just the most current version?  If the later, we
> > would find backpatching a pain for five years.
> 
> Yeah, I think we'd have to convert all the supported versions to
> make this palatable.  If the conversion is sufficiently automated,
> that might not be a big lift.  (If it's *not* automated, I think
> the change would never get off the ground even for HEAD, because
> the docs are too much of a moving target.)

+1

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Indecision is a decision.  Inaction is an action.  Mark Batterson