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 earlier if we
rsalz> wanted to open master for non-release things.
rsalz> 
rsalz> 
rsalz> On 3/20/18, 1:54 PM, "Benjamin Kaduk"  wrote:
rsalz> 
rsalz> On Wed, Mar 21, 2018 at 12:27:13AM +1000, Tim Hudson wrote:
rsalz> > We have been holding off on post-1.1.1 feature development for a 
long time
rsalz> > now - on the grounds that TLSv1.3 was just around the corner etc 
and the
rsalz> > release was close - and then we formed a release plan which we 
pushed back
rsalz> > a week.
rsalz> 
rsalz> I expect TLS 1.3 to be sent to the RFC Editor in the next day.
rsalz> 
rsalz> -Ben
rsalz> ___
rsalz> openssl-project mailing list
rsalz> openssl-project@openssl.org
rsalz> https://mta.openssl.org/mailman/listinfo/openssl-project
rsalz> 
rsalz> 
rsalz> ___
rsalz> openssl-project mailing list
rsalz> openssl-project@openssl.org
rsalz> https://mta.openssl.org/mailman/listinfo/openssl-project
___
openssl-project mailing list
openssl-project@openssl.org
https://mta.openssl.org/mailman/listinfo/openssl-project

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.

I expect TLS 1.3 to be sent to the RFC Editor in the next day.

-Ben
___
openssl-project mailing list
openssl-project@openssl.org
https://mta.openssl.org/mailman/listinfo/openssl-project


Re: [openssl-project] Code Repo

2018-03-20 Thread Salz, Rich
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 
should be working on is the release.

EVERYONE can do code reviews.

From: Tim Hudson <t...@cryptsoft.com>
Reply-To: "openssl-project@openssl.org" <openssl-project@openssl.org>
Date: Tuesday, March 20, 2018 at 10:27 AM
To: "openssl-project@openssl.org" <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 
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 forward in my 
view.
We had planned to start moving around a pile of stuff for FIPS related items - 
and keeping master locked for API changes really works against that.

There are a large range of PRs which we pushed off as must-wait-for-post-1.1.1 
and those are things that remain stalled as long as we keep master locked down.

The release for 1.1.1 should be pretty close to "complete" as such - looking at 
the plans - as with no new features going in the work remaining should be 
relatively staight forward.
Rich's suggestions I think tend to indicate more  work going into the release 
that planned - and we had said we were creating this branch - and deviating 
from that at the last minute isn't really how we shuold be making decisions as 
a project.
Some stuff that would normally be in a banch now isn't ... as Richard noted in 
the PR.

Tim.


On Wed, Mar 21, 2018 at 12:17 AM, Matt Caswell 
<m...@openssl.org<mailto:m...@openssl.org>> wrote:
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<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openssl_openssl_pull_5690=DwMFaQ=96ZbZZcaMF4w0F4jpN6LZg=4LM0GbR0h9Fvx86FtsKI-w=9Agx-vYK5V64ygDZaA-VXF-_J0Toc8LHurSEHwYFftg=_K1qiQSxWe1g7tN6OWnwtKdRuWDwZIPWo08A7cQTlGA=>
 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 previous alpha releases. However the
feature freeze *is* in force. Therefore no features can be pushed into
the repo until such time as the branch is created. All commits to master
must be suitable for inclusion in the 1.1.1 release.

Matt
___
openssl-project mailing list
openssl-project@openssl.org<mailto:openssl-project@openssl.org>
https://mta.openssl.org/mailman/listinfo/openssl-project<https://urldefense.proofpoint.com/v2/url?u=https-3A__mta.openssl.org_mailman_listinfo_openssl-2Dproject=DwMFaQ=96ZbZZcaMF4w0F4jpN6LZg=4LM0GbR0h9Fvx86FtsKI-w=9Agx-vYK5V64ygDZaA-VXF-_J0Toc8LHurSEHwYFftg=wYNJwU48t3cQS2G7emoGFewD3Bc_KuMuT00Q1v_lCuM=>

___
openssl-project mailing list
openssl-project@openssl.org
https://mta.openssl.org/mailman/listinfo/openssl-project

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 forward
in my view.
We had planned to start moving around a pile of stuff for FIPS related
items - and keeping master locked for API changes really works against that.

There are a large range of PRs which we pushed off as
must-wait-for-post-1.1.1 and those are things that remain stalled as long
as we keep master locked down.

The release for 1.1.1 should be pretty close to "complete" as such -
looking at the plans - as with no new features going in the work remaining
should be relatively staight forward.
Rich's suggestions I think tend to indicate more  work going into the
release that planned - and we had said we were creating this branch - and
deviating from that at the last minute isn't really how we shuold be making
decisions as a project.
Some stuff that would normally be in a banch now isn't ... as Richard noted
in the PR.

Tim.


On Wed, Mar 21, 2018 at 12:17 AM, Matt Caswell  wrote:

> 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 previous alpha releases. However the
> feature freeze *is* in force. Therefore no features can be pushed into
> the repo until such time as the branch is created. All commits to master
> must be suitable for inclusion in the 1.1.1 release.
>
> Matt
> ___
> openssl-project mailing list
> openssl-project@openssl.org
> https://mta.openssl.org/mailman/listinfo/openssl-project
>
___
openssl-project mailing list
openssl-project@openssl.org
https://mta.openssl.org/mailman/listinfo/openssl-project

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 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 previous alpha releases. However the
> feature freeze *is* in force. Therefore no features can be pushed into
> the repo until such time as the branch is created. All commits to master
> must be suitable for inclusion in the 1.1.1 release.
> 
> Matt
> ___
> openssl-project mailing list
> openssl-project@openssl.org
> https://mta.openssl.org/mailman/listinfo/openssl-project
> 
___
openssl-project mailing list
openssl-project@openssl.org
https://mta.openssl.org/mailman/listinfo/openssl-project


[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 previous alpha releases. However the
feature freeze *is* in force. Therefore no features can be pushed into
the repo until such time as the branch is created. All commits to master
must be suitable for inclusion in the 1.1.1 release.

Matt
___
openssl-project mailing list
openssl-project@openssl.org
https://mta.openssl.org/mailman/listinfo/openssl-project