On 21/07/16 09:56, Christian Hägele wrote:
> Am 25.06.2016, 00:27 Uhr, schrieb Matt Caswell :
>
>> The current thinking is Thursday 7th July, although that is not set in
>> stone as it depends on what happens between now and then. We don't
>> currently have any plans for a beta 3, although again
Am 25.06.2016, 00:27 Uhr, schrieb Matt Caswell :
The current thinking is Thursday 7th July, although that is not set in
stone as it depends on what happens between now and then. We don't
currently have any plans for a beta 3, although again that could change.
7th of July was 2 weeks ago.
Are t
> > And as far as regressions after beta 2 release are concerned, it looks
> > like there was a change in the API that is not backwards compatible. I
> > was hoping this would not happen after the "Beta 2 - Opaque work
> > complete". Did I misunderstand what that note means?
> >
> > The non-compati
On 24/06/16 22:28, Jouni Malinen wrote:
> On Mon, May 23, 2016 at 01:15:45PM +, Salz, Rich wrote:
>> ... in case you haven't noticed :) Our announced release date for 1.1 has
>> come and gone.
>>
>> We want to close many more bugs before we release it. In the meantime,
>> please test agai
On Mon, May 23, 2016 at 01:15:45PM +, Salz, Rich wrote:
> ... in case you haven't noticed :) Our announced release date for 1.1 has
> come and gone.
>
> We want to close many more bugs before we release it. In the meantime,
> please test against master or a daily snapshot or the last beta
When it is expected to release now?
Regards
Nikhil
-Original Message-
From: openssl-dev [mailto:openssl-dev-boun...@openssl.org] On Behalf Of Salz,
Rich
Sent: Monday, May 23, 2016 6:46 PM
To: openssl-dev@openssl.org; openssl-us...@openssl.org
Subject: [openssl-dev] 1.1 release being
... in case you haven't noticed :) Our announced release date for 1.1 has come
and gone.
We want to close many more bugs before we release it. In the meantime, please
test against master or a daily snapshot or the last beta release.
Thanks for your patience!
--
Senior Architect, Akamai Te
