Re: #10388

2019-11-15 Thread Dr Paul Dale
The consensus seems to be to add the deprecated API to 3.0. I’ve removed the hold. Pauli -- Dr Paul Dale | Distinguished Architect | Cryptographic Foundations Phone +61 7 3031 7217 Oracle Australia > On 15 Nov 2019, at 10:40 pm, Matthias St. Pierre > wrote: > > > > On 14.11.19 20:40,

Re: #10388

2019-11-15 Thread Matthias St. Pierre
On 14.11.19 20:40, Viktor Dukhovni wrote: On Nov 14, 2019, at 9:15 AM, Matt Caswell wrote: "No existing public interface can be removed until its replacement has been in place in an LTS stable release. The original interface must also have been documented as deprecated for at least 5 years.

Re: #10388

2019-11-14 Thread Viktor Dukhovni
> On Nov 14, 2019, at 9:15 AM, Matt Caswell wrote: > > "No existing public interface can be removed until its replacement has > been in place in an LTS stable release. The original interface must also > have been documented as deprecated for at least 5 years. A public > interface is any

Re: #10388

2019-11-14 Thread Matt Caswell
On 14/11/2019 13:43, Salz, Rich wrote: > *>*I’m more concerned about adding these to 3.0.  It means we’ll have to > support the new API for a long time and it is one which we are currently > trying to move away from. > >   > > Will you?  Have you already decided that 3.0 is an LTS release?  >

Re: #10388

2019-11-14 Thread Salz, Rich
>I’m more concerned about adding these to 3.0. It means we’ll have to support >the new API for a long time and it is one which we are currently trying to >move away from. Will you? Have you already decided that 3.0 is an LTS release? Otherwise, you have the LTS burden and when the rest of

Re: #10388

2019-11-14 Thread Viktor Dukhovni
On Thu, Nov 14, 2019 at 08:41:57AM +, Matt Caswell wrote: > I think that we should not add them to 1.1.1 without also adding them to 3.0. Yes. > OTOH if you have a 1.0.2 application that uses these things then not having > them would represent a barrier to moving off of 1.0.2. And it

Re: #10388

2019-11-14 Thread Matt Caswell
On 14/11/2019 06:39, Dr Paul Dale wrote: > With reference to #10388: https://github.com/openssl/openssl/pull/10388 > > This PR intends to add missing APIs to 1.1.1.  I’m fine with this being > considered a bug and adding them. > > > I’m more concerned about adding th

#10388

2019-11-13 Thread Dr Paul Dale
With reference to #10388: https://github.com/openssl/openssl/pull/10388 <https://github.com/openssl/openssl/pull/10388> This PR intends to add missing APIs to 1.1.1. I’m fine with this being considered a bug and adding them. I’m more concerned about adding these to 3.0. It means we’l