On 10/24/25 21:50, David Rowley wrote: > On Sat, 25 Oct 2025 at 17:36, Adrian Klaver <adrian.klaver@aklaver.com> wrote: >> I am not following, from your previous post: >> >> "Beta versions are meant for test instances. It'd be >> good if people encouraged their use more often rather than pushing >> people to defer til GA" >> >> That seems to be the opposite of what you say above. > > I think you think that because you misunderstood what I said in [1]. > I'll rephrase it for you: > > Because people promote the .0 as not yet production-ready, it means > that fewer people bother testing with beta and RC versions. Lack of > beta testing is what causes .0 to contain more bugs than it otherwise > might, so my suggestion is that we should be encouraging people to run > beta and RC in their test environments to try to increase the > stability of .0 versions.
Alright that I understand, though not necessarily agree with. I would say lack of testing has more to do with time/money management. Organizations don't want to spend either until: 1) They see the dust settle on what is going to end up in the release. 2) Whether there is anything interesting enough to invest both in moving to a new release. Maybe there is a compelling argument that can be made to get those organizations off the fence. I just don't what it is as you would have to convince them to spend time and money rather then just wait and let the community as a whole do the work.\
Contractual requirements to not run EOL software are a strong motivator to migrate to newer versions of OS and RDBMS.
