Daniel Stenberg wrote:
On Mon, 2 Jul 2018, Rich Gray wrote:
https://curl.haxx.se/dev/deprecate.html
I wonder if for depreciation of build options like axTLS, you should
arrange a big warning message should anyone try to build it. This may get
someone's attention when they might
it will not
include any traces of the removed thing. Except the DEPRECATE.md document
then, which will hold the explanation and deprecation history.
For a runtime option like HTTP pipelining, I guess the best one can do is to
put out a depreciated option warning when it is used and any sort
Daniel Stenberg wrote:
FYI,
I just added docs/DEPRECATE.md to the git repo, outlining the deprecation
plans for axTLS and pipelining. This document is now available on the site
here:
https://curl.haxx.se/dev/deprecate.html
When these features have been deprecated, I think they should
that is reasonable ... deprecate label is all I need. thx Jim
On 2 July 2018 at 09:39, Daniel Stenberg wrote:
> On Mon, 2 Jul 2018, James Fuller wrote:
>
>> Maybe we could raise an issue for each deprecated item (apologies for
>> being a process nazi ... just want to be able to subscribe to
On Mon, 2 Jul 2018, James Fuller wrote:
Maybe we could raise an issue for each deprecated item (apologies for being
a process nazi ... just want to be able to subscribe to them),
Sure, but I think I prefer doing an issue/PR per step/action so that we don't
need to have them linger around
Maybe we could raise an issue for each deprecated item (apologies for
being a process nazi ... just want to be able to subscribe to them),
Jim
On 2 July 2018 at 08:23, Daniel Stenberg wrote:
> FYI,
>
> I just added docs/DEPRECATE.md to the git repo, outlining the deprecation
> pla
FYI,
I just added docs/DEPRECATE.md to the git repo, outlining the deprecation
plans for axTLS and pipelining. This document is now available on the site
here:
https://curl.haxx.se/dev/deprecate.html
When these features have been deprecated, I think they should still be
mentioned
