Message-ID: <gh-pgjdbc-pgjdbc-4075-c4467988197@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Sat, 16 May 2026 20:14:21 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #4075: docs: restructure site, compatibility page, changelog-driven releases
In-Reply-To: <gh-pgjdbc-pgjdbc-4075@github.com>
References: <gh-pgjdbc-pgjdbc-4075@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: vlsi
X-GitHub-Comment-Id: 4467988197
X-GitHub-Comment-Type: issue_comment
X-GitHub-Edited-At: 2026-05-18T06:35:56Z
X-GitHub-Issue: 4075
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/4075#issuecomment-4467988197
Content-Type: text/plain; charset=utf-8

>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.