release date formatting
Hackorum builds and tests every patch posted to the lists, not only commitfest submissions. This is Hackorum's own CI rather than the PostgreSQL project's, and it is still under testing - please report anything that looks wrong.
You can run a PostgreSQL built from this patch straight from Docker, with no checkout and no build:
docker run --rm -p 5432:5432 ghcr.io/hackorum-dev/postgres-patch:t75917psql -h localhost -U postgresBuilt from patchset v1 (message #1), July 28, 2026 at 06:52 AM.
Every patchset is also pushed to a branch of our PostgreSQL fork, so you can check out the same tree CI built. Without a PostgreSQL checkout:
git clone --branch t75917_1 https://github.com/hackorum-dev/postgres.gitIn a checkout you already have, add the fork once:
git remote add hackorum https://github.com/hackorum-dev/postgres.gitthen, for this patchset and every later one:
git fetch hackorum t75917_1 && git checkout t75917_1Patchset v1 (message #1) is on t75917_1
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.)
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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.
--
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
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?
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?
Hm, actually, renaming those section IDs broke more than ease of
maintenance of the relnotes: the website no longer realizes that
https://www.postgresql.org/docs/devel/static/pgwaldump.html
has any connection to
https://www.postgresql.org/docs/9.5/static/pgxlogdump.html
although ideally the former would be seen as the latest version
of the latter. So that might provide more motivation to think
of a smarter answer here.
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-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