On Sat, 9 Nov 2024, Jeroen Ooms via curl-library wrote:

The problem is that packagers don't know about these regressions when
they visit https://curl.se/download.html so it will automatically get
pushed into many distros.

That's a primary reason why we started the curl-distros mailing list: https://lists.haxx.se/listinfo/curl-distros

To discuss regressions and share patches etc across distros shipping curl.

For the same reason, many of us are dealing with several with problems in libcurl 8.7.1 which is the production version on MacOS for this year because it was the latest "stable" when apple updated their OS stack. However it had several known regressions.

I strongly disagree. That's entirely their (Apple's) fault and nobody else's. They did not do their homework. If Apple doesn't have the competence to do it properly themselves, I would happily offer this service to them.

Perhaps it could be discussed to consider a policy in the future to
officially mark regressed releases as such.

*every* release has regressions, so consider everyone marked as a release with regressions. The difference between them is if the regressions are important to you or not, which is hard for anyone else to say.

If we scare people away from downloading and using the latest, we will just delay the finding of the regressions and the problem will just grow larger over time, not smaller.

Our "real" fix for regressions is to do a patch release sooner rather than later so that the largest effects from the regressions can swiftly be upgraded away.

For commercial businesses scared of regressions, we offer regression-free curl releases under the Rock-solid curl umbrella. That's not work we do for free.

--

 / daniel.haxx.se || https://rock-solid.curl.dev
--
Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library
Etiquette:   https://curl.se/mail/etiquette.html

Reply via email to