pgjdbc/pgjdbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feedFrom: vlsi (@vlsi) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: Re: [pgjdbc/pgjdbc] PR #4075: docs: restructure site, compatibility page, changelog-driven releases
Date: Sat, 16 May 2026 20:14:21 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
>I forgot to say. In general, I really like it
Glad to hear it.
> we should be making it easy for agents to read
That is a non-goal for the current PR.
The goal for the current PR is to make the page easy for humans.
Semantic html, agents, and other changes should go afterwards in a separate PR otherwise we never merge this.
> We should make this so that it can be generated with github pages so we don't have to upload this to jdbc.postgresql.org
I do not think it is related to the current PR.
It should be done independently. The PR keeps pretty much the same website build flow except it adds metadata extraction from git history (release timeline) and java bytecode (property reference).
> As far as the pages go it appears that part of this is establishing an EOL policy that we have not discussed
Comments are welcome. The page `getting-started/compatibility/` sets more **relaxed** expectations than what we currently have in https://github.com/pgjdbc/pgjdbc/blob/master/SECURITY.md
If you think we need to tighten them, I'm fine.
If you think we should relax it even more, I am not really sure. Suggest reasons.
view thread (64+ messages) latest in thread
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: github://pgjdbc/pgjdbc
Cc: [email protected], [email protected]
Subject: Re: [pgjdbc/pgjdbc] PR #4075: docs: restructure site, compatibility page, changelog-driven releases
In-Reply-To: <<[email protected]>>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox