Forthcoming OpenSSL releases
The OpenSSL project team would like to announce the forthcoming release
of OpenSSL versions 1.1.0h and 1.0.2o.
These releases will be made available on 27th March 2018 between
approximately 1300-1700 UTC.
These are security-fix releases.
I didn't say that I wanted to do this, I just said that we could. I very
strongly believe that the team should be working on nothing else until the
release is out. If some people feel they need to get post-release stuff
checked into the tree, this is one way to do it.
On 3/20/18, 2:03 PM, "R
This should include the fix to the bug Guido found.
On 3/20/18, 1:18 PM, "Matt Caswell" wrote:
Forthcoming OpenSSL releases
The OpenSSL project team would like to announce the forthcoming release
of OpenSSL versions 1.1.0h and 1.0.2o.
T
Why do you want to rush it? A month earlier than what we've currently
scheduled is in 4 weeks. I think the added stress will do nothing
good for us, or our community.
In message on Tue, 20 Mar
2018 17:57:45 +, "Salz, Rich" said:
rsalz> Therefore, we could have the release done a month ea
Therefore, we could have the release done a month earlier if we wanted to open
master for non-release things.
On 3/20/18, 1:54 PM, "Benjamin Kaduk" wrote:
On Wed, Mar 21, 2018 at 12:27:13AM +1000, Tim Hudson wrote:
> We have been holding off on post-1.1.1 feature development for a lon
On Wed, Mar 21, 2018 at 12:27:13AM +1000, Tim Hudson wrote:
> We have been holding off on post-1.1.1 feature development for a long time
> now - on the grounds that TLSv1.3 was just around the corner etc and the
> release was close - and then we formed a release plan which we pushed back
> a week.
On 20/03/18 15:49, Dr. Matthias St. Pierre wrote:
>
> Even more statistics: the completion rate of the milestone has
> _dropped_ from 30% to 26% since yesterday:
> https://github.com/openssl/openssl/milestone/9
That will be because I went through all recent PRs and issues and added
them to a m
Even more statistics: the completion rate of the milestone has
_dropped_ from 30% to 26% since yesterday:
https://github.com/openssl/openssl/milestone/9
Matthias
Am 20.03.2018 um 16:06 schrieb Matt Caswell:
> Without stating an opinion either way - some stats:
>
> PRs with 1.1.1 milestone: 57
Without stating an opinion either way - some stats:
PRs with 1.1.1 milestone: 57
Issues with 1.1.1 milestone: 160
Coverity Issues: 68
All of the above need to be resolved (possibly by deferring them), plus
any new ones that get raised in the meantime, before we can release.
Matt
On 20/03/18 14
We still have a lot of work to do to meet our release goals. It was really bad
last time and we definitely lost our focus multiple times.
If in two weeks we get everything done and we’re just sitting aroun waiting for
the IETF to publish, great. But if not, I strongly believe the only thing we
We have been holding off on post-1.1.1 feature development for a long time
now - on the grounds that TLSv1.3 was just around the corner etc and the
release was close - and then we formed a release plan which we pushed back
a week.
It is long overdue that we get to start moving those other things f
Of course I should have mentioned that although the feature freeze is in
place, the code freeze is not, i.e. you can make pushes to the repo now.
Matt
On 20/03/18 14:17, Matt Caswell wrote:
> The beta release is now complete.
>
> Important:
>
> We did *not* create the OpenSSL_1_1_1-stable bran
The beta release is now complete.
Important:
We did *not* create the OpenSSL_1_1_1-stable branch as planned (see
https://github.com/openssl/openssl/pull/5690 for the discussion that led
to that decision). For now the release was done from the master branch
in the same way as we did for the previo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 1.1.1 pre release 3 (beta)
===
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
OpenSSL 1.1.1 is currently in beta. OpenSSL 1.1.1 pre release 3 has now
14 matches
Mail list logo
