On Mon, Aug 31, 2026 at 12:47:09PM -0400, Bruce Momjian wrote: > We know we will have to have another beta to test after removing > multiple features. > > It feels we are in an unprecedented situation here.
It is and importantly, this speaks to confidence in the release. With the number of reverts being discussed, confidence in this release (whether we revert the features or not) is lower. Instead, I propose we shift the release to Spring of 2027. This will help in a number of ways: 1. Allow the features to mature and make a deterministic decision about their quality over time. 2. If we treat it as the new timeline, we remove a long-standing issue with the development cycle: Our testing window is in summer. I have not had any customer tell me they are blocked, or "needing" 19. Heck, most people don't even run 18 so why are we in such a hurry? I would rather have a late 19 than all these great features and hard work gutted. JD -- - Founder - https://commandprompt.com/ - 24x7x365 Postgres since 1997 - Founder and Co-Chair - https://postgresconf.org/ - Founder - https://postgresql.us - United States PostgreSQL - Public speaker, published author, postgresql expert, and people believer. - Host - More than a refresh: A podcast about data and the people who wrangle it.
