<div dir="auto">Sorry. My fault :(</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 7 Jan 2020, 16:35 Matt Caswell, <<a href="mailto:matt@openssl.org">matt@openssl.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
On 07/01/2020 13:26, Dmitry Belyavsky wrote:<br>
> Many thanks!<br>
> <br>
> Got it, and I think this should be directly written. <br>
<br>
It was!!<br>
<br>
beta1, 2020-06-02: Code complete (API stable, feature freeze)<br>
<br>
<br>
Matt<br>
<br>
<br>
> <br>
> On Tue, 7 Jan 2020, 16:05 Matt Caswell, <<a href="mailto:matt@openssl.org" target="_blank" rel="noreferrer">matt@openssl.org</a><br>
> <mailto:<a href="mailto:matt@openssl.org" target="_blank" rel="noreferrer">matt@openssl.org</a>>> wrote:<br>
> <br>
> <br>
> <br>
> On 07/01/2020 13:00, Dmitry Belyavsky wrote:<br>
> > When does the feature freeze happen?<br>
> > I'm interested in publishing as much GOST support as possible.<br>
> <br>
> According to my proposal feature freeze would happen on release of<br>
> beta1, i.e. 2020-06-02.<br>
> <br>
> Matt<br>
> <br>
> <br>
> ><br>
> > On Tue, 7 Jan 2020, 14:13 Matt Caswell, <<a href="mailto:matt@openssl.org" target="_blank" rel="noreferrer">matt@openssl.org</a><br>
> <mailto:<a href="mailto:matt@openssl.org" target="_blank" rel="noreferrer">matt@openssl.org</a>><br>
> > <mailto:<a href="mailto:matt@openssl.org" target="_blank" rel="noreferrer">matt@openssl.org</a> <mailto:<a href="mailto:matt@openssl.org" target="_blank" rel="noreferrer">matt@openssl.org</a>>>> wrote:<br>
> ><br>
> > Hi all<br>
> ><br>
> > Myself, Paul, Shane, Richard and Nicola had a conf call today<br>
> to discuss<br>
> > the outstanding tasks and effort required to get us to a final<br>
> release.<br>
> ><br>
> > We've previously said this about that timeline:<br>
> ><br>
> > "We are now not expecting code completion to occur until the<br>
> end of Q2<br>
> > 2020 with a final release in early Q4 2020."<br>
> > (<a href="https://www.openssl.org/blog/blog/2019/11/07/3.0-update/" rel="noreferrer noreferrer" target="_blank">https://www.openssl.org/blog/blog/2019/11/07/3.0-update/</a>)<br>
> ><br>
> ><br>
> > With that in mind we came up with the following proposal for a<br>
> release<br>
> > timetable which we think is a challenging but achievable timeline:<br>
> ><br>
> > alpha1, 2020-03-31: Basic functionality plus basic FIPS module<br>
> > alpha2, 2020-04-21: Complete external provider support<br>
> (serialization,<br>
> > support for new algs, support for providers which only include<br>
> > operations in a class)<br>
> > alpha3, 2020-05-21: Almost there (aiming to test the API<br>
> completeness<br>
> > before beta1 freezes it)<br>
> > beta1, 2020-06-02: Code complete (API stable, feature freeze)<br>
> > betaN: Other beta TBD<br>
> > Final: 2020 early Q4<br>
> ><br>
> > The idea here is to set some intermediate deadlines to focus<br>
> attention<br>
> > on the final remaining tasks, with a series of 3 alphas prior<br>
> to the<br>
> > first beta release where each alpha release comes<br>
> approximately every 3<br>
> > weeks. We can have some flexibility to adjust this timetable<br>
> if we think<br>
> > it is necessary (such as by including an additional alpha<br>
> release if<br>
> > required).<br>
> ><br>
> > Please let me know your thoughts. This would probably need to<br>
> go to an<br>
> > OMC vote to get approved.<br>
> ><br>
> > Matt<br>
> ><br>
> <br>
</blockquote></div>