| ▲ | ltbarcly3 3 hours ago | |||||||
I have found major bugs in late beta's of postgres long before AI came along. I found a bug where malformed json would segfault the entire server (a segfault in a server process forces the entire cluster to shut down by design) when using jsonb in a release candidate once. They fixed it rather than ripping the entire feature out. https://www.postgresql.org/message-id/20140818195634.2543.56... It seems quite possible that someone wants to make it seem like LLMs are causing problems by over-reacting to things that could just be fixed, or delay the release slightly (or maybe waiting until late before a release to kill features they don't like?) Whatever it is, this seems like a dysfunctional process. | ||||||||
| ▲ | benjiro29 3 hours ago | parent | next [-] | |||||||
Maybe its more a issue that X amount of people have more work to fix discovered issues. So the new features have not undergone the same level of testing as before. And instead of releasing substandard new features, they rather focus on getting rid of the backlog and have more time to test. LLMs are in effect directly responsible for this (in a positive way by finding a ton of issues that can be security issues). Reality is with LLMs now in the world, more work needs to be done on existing software as their ability to find bugs/security weaknesses is strong. When the old bugs/security weaknesses are fixed, things will go back to a more normal release schedule. | ||||||||
| ||||||||
| ▲ | StilesCrisis 3 hours ago | parent | prev [-] | |||||||
If you are at the RC stage and still uncovering segfaults, "rip the feature out" is probably the only choice. | ||||||||