Horton

Re: Security lessons from liblzma

Joe Conway <mail@joeconway.com>

View thread
From: Joe Conway <mail@joeconway.com>
To: Andres Freund <andres@anarazel.de>, Robert Haas <robertmhaas@gmail.com>
Cc: Bruce Momjian <bruce@momjian.us>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2024-03-31T00:05:59Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Introduce a non-recursive JSON parser

On 3/30/24 19:54, Joe Conway wrote:
>> On 2024-03-30 16:50:26 -0400, Robert Haas wrote:
>>> or what Tom does when he builds the release tarballs.
> 
> Tom follows this, at least last time I checked:
> 
> https://wiki.postgresql.org/wiki/Release_process

Reading through that, I wonder if this part is true anymore:

   In principle this could be done anywhere, but again there's a concern
   about reproducibility, since the results may vary depending on
   installed bison, flex, docbook, etc versions. Current practice is to
   always do this as pgsql on borka.postgresql.org, so it can only be
   done by people who have a login there. In detail:

Maybe if we split out the docs from the release tarball, we could also 
add the script (mk-release) to our git repo?

Some other aspects of that wiki page look out of date too. Perhaps it 
needs an overall update? Maybe Tom and/or Magnus could weigh in here.

-- 
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com