pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: pgsql-docs@postgresql.org
Subject: Re: release date formatting
Date: Fri, 12 May 2017 22:08:05 -0400
Message-ID: <20170513020805.GA4673@momjian.us> (raw)
In-Reply-To: <19299.1494632547@sss.pgh.pa.us>
References: <2b8a2552-fffa-f7c8-97c5-14db47a87731@2ndquadrant.com>
	<20170512223328.GB31631@momjian.us>
	<19299.1494632547@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-docs>

On Fri, May 12, 2017 at 07:42:27PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > On Tue, May  2, 2017 at 12:35:06PM -0400, Peter Eisentraut wrote:
> >> It has been pointed out a while ago that the "release date" formatting
> >> in the release notes is too flamboyant, more so under the new stylesheets.
> >> 
> >> Here is a patch to make the formatting a bit more subdued.  (Obviously,
> >> this needs to be expanded to older release notes as well.)
> 
> > I see what you mean.  I have changed the markup in head for all branches
> > and backpatched this so when we copy release information to back
> > branches, it matches.
> 
> I'm a bit dubious about this: it may make things look nicer with the new
> docs toolchain, but did anyone check what it looks like with the old one?

I did not but the <note> tag really never made sense for the release
note date anyway, so I assumed it would be fine.

> Also, now that you mention it, the ability to copy relnote files into
> older branches verbatim was already broken by commit 85c11324c.  I got
> burnt by this while making the release notes last weekend, and was quite
> annoyed but there was no time to do anything about it then.  Is there
> a way to fix that, perhaps by providing some kind of alias for the
> relevant section IDs?

Yes, I noticed that myself so I assume we would have to copy just the
new _sections_ to the back branches, instead of copying the entire file
like we have done in the past, at least until this was fixed.

-- 
  Bruce Momjian  <bruce@momjian.us>        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 +


-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs



view thread (4+ messages)

Message-ID: <20170513020805.GA4673@momjian.us>
Permalink:  ../20170513020805.GA4673@momjian.us/
Also on:    postgresql.org/message-id/20170513020805.GA4673@momjian.us

 · 

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: pgsql-docs@postgresql.org
  Cc: bruce@momjian.us, tgl@sss.pgh.pa.us, peter.eisentraut@2ndquadrant.com
  Subject: Re: release date formatting
  In-Reply-To: <20170513020805.GA4673@momjian.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox