Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d9MTb-00074y-JI for pgsql-docs@arkaria.postgresql.org; Sat, 13 May 2017 02:08:11 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1d9MTb-0005x4-42 for pgsql-docs@arkaria.postgresql.org; Sat, 13 May 2017 02:08:11 +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.84_2) (envelope-from ) id 1d9MTa-0005wu-Mu for pgsql-docs@postgresql.org; Sat, 13 May 2017 02:08:10 +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.84_2) (envelope-from ) id 1d9MTW-0005tO-Uz for pgsql-docs@postgresql.org; Sat, 13 May 2017 02:08:10 +0000 Received: from bruce by momjian.us with local (Exim 4.84_2) (envelope-from ) id 1d9MTV-0001qF-30; Fri, 12 May 2017 22:08:05 -0400 Date: Fri, 12 May 2017 22:08:05 -0400 From: Bruce Momjian To: Tom Lane Cc: Peter Eisentraut , pgsql-docs@postgresql.org Subject: Re: release date formatting Message-ID: <20170513020805.GA4673@momjian.us> References: <2b8a2552-fffa-f7c8-97c5-14db47a87731@2ndquadrant.com> <20170512223328.GB31631@momjian.us> <19299.1494632547@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <19299.1494632547@sss.pgh.pa.us> User-Agent: Mutt/1.5.23 (2014-03-12) X-Pg-Spam-Score: -1.9 (-) 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 Fri, May 12, 2017 at 07:42:27PM -0400, Tom Lane wrote: > Bruce Momjian 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 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 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