Re: [openssl-project] Code Repo

2018-03-20 Thread Salz, Rich
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

Re: [openssl-project] Code Repo

2018-03-20 Thread Richard Levitte
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

Re: [openssl-project] Code Repo

2018-03-20 Thread Salz, Rich
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

Re: [openssl-project] Code Repo

2018-03-20 Thread Benjamin Kaduk
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.

Re: [openssl-project] Code Repo

2018-03-20 Thread Matt Caswell
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

Re: [openssl-project] Code Repo

2018-03-20 Thread Dr. Matthias St. Pierre
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

Re: [openssl-project] Code Repo

2018-03-20 Thread Matt Caswell
10:27 AM > *To: *"openssl-project@openssl.org" > *Subject: *Re: [openssl-project] Code Repo > >   > > 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 w

Re: [openssl-project] Code Repo

2018-03-20 Thread Salz, Rich
should be working on is the release. EVERYONE can do code reviews. From: Tim Hudson Reply-To: "openssl-project@openssl.org" Date: Tuesday, March 20, 2018 at 10:27 AM To: "openssl-project@openssl.org" Subject: Re: [openssl-project] Code Repo We have been holding off o

Re: [openssl-project] Code Repo

2018-03-20 Thread Tim Hudson
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

Re: [openssl-project] Code Repo

2018-03-20 Thread Matt Caswell
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

[openssl-project] Code Repo

2018-03-20 Thread Matt Caswell
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