Re: [openssl-project] Accept PR 5702 after the feature-freeze?

To increase transparency, you could also add a clause which ensures that every exceptional merge needs to be announced on openssl-project: A pull request that introduces a new feature can be merged regardless of the feature freeze, if it is related to TLS 1.3 and approved by at

Re: [openssl-project] Accept PR 5702 after the feature-freeze?

Yes, that is a good idea! On 3/21/18, 4:29 PM, "Matt Caswell" wrote: On 21/03/18 20:23, Dr. Matthias St. Pierre wrote: > Not that it's my business, but IMHO it might be sensible to loosen the > freeze for TLS 1.3 related changes in general, since that

[openssl-project] Accept PR 5702 after the feature-freeze?

https://github.com/openssl/openssl/pull/5702 It is after our declared feature-freeze. I think we should allow this PR. From the description: NSS 3.34 and boringssl have support for "EXPORTER_SECRET" (https://bugzilla.mozilla.org/show_bug.cgi?id=1287711) which is