> It might be sort of subjective but I don't think there's anything wrong with 
> that. It's one of those things you know it when you see it.

Yes, I agree.
For me release patch considerations are always a trade-off between the 
following major arguments :
- Is the issue quite serious and have a big impact. 
- Is there any workaround and it is acceptable (simple enough to apply for 
mitigating the issue for majority of cases with the biggest impact).
- Is there a bug fix and it can be applied with a no/minimal risk to create 
more regressions.

If the consideration (which is sort of subjective, as Ray put it)  results into 
the following conclusion:
- Issue is serious, has a big impact and needs to be handled ASAP.
- No simple and/or acceptable workaround.
- There is a simple and localized bug fix with a very minimal chance of new 
regressions.

then these considerations create an initial justification for a patch release 
for me.

Of course, each item can be broken into more specific details (crashes, 
security issues etc), which may need further consideration, 
but basic justifications for a patch release can be summarized in just a few 
major things.

Thanks,
Dmitry Karpov

-----Original Message-----
From: curl-library <curl-library-boun...@lists.haxx.se> On Behalf Of Ray Satiro 
via curl-library
Sent: Thursday, October 27, 2022 2:45 PM
To: curl-library@lists.haxx.se
Cc: Ray Satiro <raysat...@yahoo.com>
Subject: [EXTERNAL] Re: noproxy breakage

On 10/27/2022 5:29 PM, Daniel Stenberg via curl-library wrote:
>
> A regression in the noproxy filter functionality in 7.86.0 has been 
> suggested to be reason enough for a patch release:
>
> https://github.com/curl/curl/issues/9813

I'm for patch releases for issues like that.


> We don't yet have any stated policy for how to judge when a bug is 
> reason enough for a patch release but maybe this is the time to try to 
> forumlate a guideline?

It might be sort of subjective but I don't think there's anything wrong with 
that. It's one of those things you know it when you see it.


-- 
Unsubscribe: https://lists.haxx.se/listinfo/curl-library
Etiquette:   https://curl.se/mail/etiquette.html
-- 
Unsubscribe: https://lists.haxx.se/listinfo/curl-library
Etiquette:   https://curl.se/mail/etiquette.html

Reply via email to