Re: [openssl-project] Next release is beta1

2018-03-05 Thread Matt Caswell
On 04/03/18 16:30, Kurt Roeckx wrote: > On Sun, Mar 04, 2018 at 02:44:01PM +, Salz, Rich wrote: >> I also intend to merge the config file .include PR (5351), and I want us to >> decide about 4848. > > I have to agree that I want to resolv 4848 (reading config file to > select things like

Re: [openssl-project] Next release is beta1

2018-03-04 Thread Benjamin Kaduk
On Sun, Mar 04, 2018 at 05:30:32PM +0100, Kurt Roeckx wrote: > On Sun, Mar 04, 2018 at 02:44:01PM +, Salz, Rich wrote: > > I also intend to merge the config file .include PR (5351), and I want us to > > decide about 4848. > > I have to agree that I want to resolv 4848 (reading config file to

Re: [openssl-project] Next release is beta1

2018-03-04 Thread Kurt Roeckx
On Sun, Mar 04, 2018 at 02:44:01PM +, Salz, Rich wrote: > I also intend to merge the config file .include PR (5351), and I want us to > decide about 4848. I have to agree that I want to resolv 4848 (reading config file to select things like supported ciphers.) An other important change is

Re: [openssl-project] Next release is beta1

2018-03-04 Thread Salz, Rich
Kurt raises an excellent point. I want this in the release: https://github.com/openssl/openssl/pull/5438 I want discussion about these two, hopefully concluding that they be in the release: https://github.com/openssl/openssl/pull/5326

Re: [openssl-project] Next release is beta1

2018-03-04 Thread Kurt Roeckx
On Fri, Mar 02, 2018 at 11:09:30AM +, Matt Caswell wrote: > Just a reminder, in case anyone missed it, that our next planned release > on 13th March is beta1. This means we will be calling a feature freeze > for 1.1.1 and we will create the new branch. If you've got any > outstanding feature