Message-ID: From: "sehrope (@sehrope)" To: "pgjdbc/pgjdbc" Date: Fri, 22 May 2026 12:54:19 +0000 Subject: Re: [pgjdbc/pgjdbc] PR #4075: docs: restructure site, compatibility page, changelog-driven releases In-Reply-To: References: List-Id: X-GitHub-Author-Login: sehrope X-GitHub-Comment-Id: 4518817471 X-GitHub-Comment-Type: issue_comment X-GitHub-Edited-At: 2026-05-22T13:23:08Z X-GitHub-Issue: 4075 X-GitHub-Repo: pgjdbc/pgjdbc X-GitHub-Type: comment X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/4075#issuecomment-4518817471 Content-Type: text/plain; charset=utf-8 Anything of this magnitude, whether more tooling, code change, docs change, or both (as is here) needs to have a wider acceptance before it starts. It's fine to experiment on your fork and see what comes out. It's fine to create the patch too and use it as an example of what you want to do. But it's not reasonable to make 14000+ line changes and expect others to review and sign off on them. I really see no way of this PR ever being merged. I think we should just reject it and take it as a lesson of how __not__ to make gigantic repo wide changes. If you want to redo the site, figure out a way to do it piecemeal that allows the incremental pieces to actually be reviewed. By humans, not just more AI. The documentation is in English and if that's not your native language, it probably means you shouldn't be wholesale replacing it as it's not possible to self review. It'd be like me replacing all the Russian message translations! And without a meaningful self review process, you're creating an inordinate amount of work for others. Each comment or reply in this thread has generated 1000+ diffs of new items. And that's from us barely skimming through it.