Re: AW: 3.0 release timeline proposal

[Matt Caswell]

On 07/01/2020 17:00, Brockhaus, Hendrik wrote:
> Hi Matt
> 
> Currently David and Andreas are contributing the mpeylo/cmpossl code. We want 
> to get the complete CMP code upstream OpenSSL v3.0 as soon as possible.
> Currently chunk 7 (https://github.com/openssl/openssl/pull/10620) is under 
> review and chunk 8 is available as work-in-progress 
> (https://github.com/mpeylo/cmpossl/pull/201).
> Special thanks go to you, Bend and all others in the project for your 
> continuous review effort and discussion!!
> 
> Regarding the release timeline I have two questions:
> What is the deadline for the last chunk to be merged?

If my proposed timeline is accepted then the final deadline would be the
beta1 release (2020-06-02). However it would be a good idea to target
one of the earlier alpha releases in order to gain the benefit of any
community feedback on the alpha releases that we might receive.


> The planning and current status on the contribution is available on 
> https://github.com/mpeylo/cmpossl/wiki. Do you see this timeline as realistic?

It looks reasonable to me.

Matt



> 
> Hendrik
> 
>> --
>>
>> Date: Tue, 7 Jan 2020 11:13:21 +
>> From: Matt Caswell 
>> To: "openssl-project@openssl.org" 
>> Subject: 3.0 release timeline proposal
>> Message-ID: 
>> Content-Type: text/plain; charset=utf-8
>>
>> Hi all
>>
>> Myself, Paul, Shane, Richard and Nicola had a conf call today to discuss the
>> outstanding tasks and effort required to get us to a final release.
>>
>> We've previously said this about that timeline:
>>
>> "We are now not expecting code completion to occur until the end of Q2
>> 2020 with a final release in early Q4 2020."
>> (https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ope
>> nssl.org%2Fblog%2Fblog%2F2019%2F11%2F07%2F3.0-
>> update%2Fdata=02%7C01%7Chendrik.brockhaus%40siemens.com%7C77
>> e33a0111644f055dbc08d793753718%7C38ae3bcd95794fd4addab42e1495d55a
>> %7C1%7C0%7C637140003954238503sdata=mkfVH1I2WaOwKwjqPamGZ
>> N%2FTAdrmTuH3avswGCVZmhk%3Dreserved=0)
>>
>>
>> With that in mind we came up with the following proposal for a release
>> timetable which we think is a challenging but achievable timeline:
>>
>> alpha1, 2020-03-31: Basic functionality plus basic FIPS module alpha2, 
>> 2020-04-
>> 21: Complete external provider support (serialization, support for new algs,
>> support for providers which only include operations in a class) alpha3, 
>> 2020-05-
>> 21: Almost there (aiming to test the API completeness before beta1 freezes 
>> it)
>> beta1, 2020-06-02: Code complete (API stable, feature freeze)
>> betaN: Other beta TBD
>> Final: 2020 early Q4
>>
>> The idea here is to set some intermediate deadlines to focus attention on the
>> final remaining tasks, with a series of 3 alphas prior to the first beta 
>> release
>> where each alpha release comes approximately every 3 weeks. We can have
>> some flexibility to adjust this timetable if we think it is necessary (such 
>> as by
>> including an additional alpha release if required).
>>
>> Please let me know your thoughts. This would probably need to go to an OMC
>> vote to get approved.
>>
>> Matt
> 

AW: 3.0 release timeline proposal

[Brockhaus, Hendrik]

Hi Matt

Currently David and Andreas are contributing the mpeylo/cmpossl code. We want 
to get the complete CMP code upstream OpenSSL v3.0 as soon as possible.
Currently chunk 7 (https://github.com/openssl/openssl/pull/10620) is under 
review and chunk 8 is available as work-in-progress 
(https://github.com/mpeylo/cmpossl/pull/201).
Special thanks go to you, Bend and all others in the project for your 
continuous review effort and discussion!!

Regarding the release timeline I have two questions:
What is the deadline for the last chunk to be merged?
The planning and current status on the contribution is available on 
https://github.com/mpeylo/cmpossl/wiki. Do you see this timeline as realistic?

Hendrik

> --
> 
> Date: Tue, 7 Jan 2020 11:13:21 +
> From: Matt Caswell 
> To: "openssl-project@openssl.org" 
> Subject: 3.0 release timeline proposal
> Message-ID: 
> Content-Type: text/plain; charset=utf-8
> 
> Hi all
> 
> Myself, Paul, Shane, Richard and Nicola had a conf call today to discuss the
> outstanding tasks and effort required to get us to a final release.
> 
> We've previously said this about that timeline:
> 
> "We are now not expecting code completion to occur until the end of Q2
> 2020 with a final release in early Q4 2020."
> (https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ope
> nssl.org%2Fblog%2Fblog%2F2019%2F11%2F07%2F3.0-
> update%2Fdata=02%7C01%7Chendrik.brockhaus%40siemens.com%7C77
> e33a0111644f055dbc08d793753718%7C38ae3bcd95794fd4addab42e1495d55a
> %7C1%7C0%7C637140003954238503sdata=mkfVH1I2WaOwKwjqPamGZ
> N%2FTAdrmTuH3avswGCVZmhk%3Dreserved=0)
> 
> 
> With that in mind we came up with the following proposal for a release
> timetable which we think is a challenging but achievable timeline:
> 
> alpha1, 2020-03-31: Basic functionality plus basic FIPS module alpha2, 
> 2020-04-
> 21: Complete external provider support (serialization, support for new algs,
> support for providers which only include operations in a class) alpha3, 
> 2020-05-
> 21: Almost there (aiming to test the API completeness before beta1 freezes it)
> beta1, 2020-06-02: Code complete (API stable, feature freeze)
> betaN: Other beta TBD
> Final: 2020 early Q4
> 
> The idea here is to set some intermediate deadlines to focus attention on the
> final remaining tasks, with a series of 3 alphas prior to the first beta 
> release
> where each alpha release comes approximately every 3 weeks. We can have
> some flexibility to adjust this timetable if we think it is necessary (such 
> as by
> including an additional alpha release if required).
> 
> Please let me know your thoughts. This would probably need to go to an OMC
> vote to get approved.
> 
> Matt

Re: 3.0 release timeline proposal

[Matt Caswell]

I converted this proposal into a PR to amend the release strategy.
Please see:

https://github.com/openssl/web/pull/154

Matt


On 07/01/2020 11:13, Matt Caswell wrote:
> Hi all
> 
> Myself, Paul, Shane, Richard and Nicola had a conf call today to discuss
> the outstanding tasks and effort required to get us to a final release.
> 
> We've previously said this about that timeline:
> 
> "We are now not expecting code completion to occur until the end of Q2
> 2020 with a final release in early Q4 2020."
> (https://www.openssl.org/blog/blog/2019/11/07/3.0-update/)
> 
> 
> With that in mind we came up with the following proposal for a release
> timetable which we think is a challenging but achievable timeline:
> 
> alpha1, 2020-03-31: Basic functionality plus basic FIPS module
> alpha2, 2020-04-21: Complete external provider support (serialization,
> support for new algs, support for providers which only include
> operations in a class)
> alpha3, 2020-05-21: Almost there (aiming to test the API completeness
> before beta1 freezes it)
> beta1, 2020-06-02: Code complete (API stable, feature freeze)
> betaN: Other beta TBD
> Final: 2020 early Q4
> 
> The idea here is to set some intermediate deadlines to focus attention
> on the final remaining tasks, with a series of 3 alphas prior to the
> first beta release where each alpha release comes approximately every 3
> weeks. We can have some flexibility to adjust this timetable if we think
> it is necessary (such as by including an additional alpha release if
> required).
> 
> Please let me know your thoughts. This would probably need to go to an
> OMC vote to get approved.
> 
> Matt
> 

Re: 3.0 release timeline proposal

[Dmitry Belyavsky]

Sorry. My fault :(

On Tue, 7 Jan 2020, 16:35 Matt Caswell,  wrote:

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

Re: 3.0 release timeline proposal

[Dmitry Belyavsky]

Many thanks!

Got it, and I think this should be directly written.

On Tue, 7 Jan 2020, 16:05 Matt Caswell,  wrote:

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

Re: 3.0 release timeline proposal

[Matt Caswell]

On 07/01/2020 13:00, Dmitry Belyavsky wrote:
> When does the feature freeze happen?
> I'm interested in publishing as much GOST support as possible. 

According to my proposal feature freeze would happen on release of
beta1, i.e. 2020-06-02.

Matt


> 
> On Tue, 7 Jan 2020, 14:13 Matt Caswell,  > wrote:
> 
> Hi all
> 
> Myself, Paul, Shane, Richard and Nicola had a conf call today to discuss
> the outstanding tasks and effort required to get us to a final release.
> 
> We've previously said this about that timeline:
> 
> "We are now not expecting code completion to occur until the end of Q2
> 2020 with a final release in early Q4 2020."
> (https://www.openssl.org/blog/blog/2019/11/07/3.0-update/)
> 
> 
> With that in mind we came up with the following proposal for a release
> timetable which we think is a challenging but achievable timeline:
> 
> alpha1, 2020-03-31: Basic functionality plus basic FIPS module
> alpha2, 2020-04-21: Complete external provider support (serialization,
> support for new algs, support for providers which only include
> operations in a class)
> alpha3, 2020-05-21: Almost there (aiming to test the API completeness
> before beta1 freezes it)
> beta1, 2020-06-02: Code complete (API stable, feature freeze)
> betaN: Other beta TBD
> Final: 2020 early Q4
> 
> The idea here is to set some intermediate deadlines to focus attention
> on the final remaining tasks, with a series of 3 alphas prior to the
> first beta release where each alpha release comes approximately every 3
> weeks. We can have some flexibility to adjust this timetable if we think
> it is necessary (such as by including an additional alpha release if
> required).
> 
> Please let me know your thoughts. This would probably need to go to an
> OMC vote to get approved.
> 
> Matt
> 

Re: 3.0 release timeline proposal

[Dmitry Belyavsky]

When does the feature freeze happen?
I'm interested in publishing as much GOST support as possible.

On Tue, 7 Jan 2020, 14:13 Matt Caswell,  wrote:

> Hi all
>
> Myself, Paul, Shane, Richard and Nicola had a conf call today to discuss
> the outstanding tasks and effort required to get us to a final release.
>
> We've previously said this about that timeline:
>
> "We are now not expecting code completion to occur until the end of Q2
> 2020 with a final release in early Q4 2020."
> (https://www.openssl.org/blog/blog/2019/11/07/3.0-update/)
>
>
> With that in mind we came up with the following proposal for a release
> timetable which we think is a challenging but achievable timeline:
>
> alpha1, 2020-03-31: Basic functionality plus basic FIPS module
> alpha2, 2020-04-21: Complete external provider support (serialization,
> support for new algs, support for providers which only include
> operations in a class)
> alpha3, 2020-05-21: Almost there (aiming to test the API completeness
> before beta1 freezes it)
> beta1, 2020-06-02: Code complete (API stable, feature freeze)
> betaN: Other beta TBD
> Final: 2020 early Q4
>
> The idea here is to set some intermediate deadlines to focus attention
> on the final remaining tasks, with a series of 3 alphas prior to the
> first beta release where each alpha release comes approximately every 3
> weeks. We can have some flexibility to adjust this timetable if we think
> it is necessary (such as by including an additional alpha release if
> required).
>
> Please let me know your thoughts. This would probably need to go to an
> OMC vote to get approved.
>
> Matt
>

3.0 release timeline proposal

[Matt Caswell]

Hi all

Myself, Paul, Shane, Richard and Nicola had a conf call today to discuss
the outstanding tasks and effort required to get us to a final release.

We've previously said this about that timeline:

"We are now not expecting code completion to occur until the end of Q2
2020 with a final release in early Q4 2020."
(https://www.openssl.org/blog/blog/2019/11/07/3.0-update/)


With that in mind we came up with the following proposal for a release
timetable which we think is a challenging but achievable timeline:

alpha1, 2020-03-31: Basic functionality plus basic FIPS module
alpha2, 2020-04-21: Complete external provider support (serialization,
support for new algs, support for providers which only include
operations in a class)
alpha3, 2020-05-21: Almost there (aiming to test the API completeness
before beta1 freezes it)
beta1, 2020-06-02: Code complete (API stable, feature freeze)
betaN: Other beta TBD
Final: 2020 early Q4

The idea here is to set some intermediate deadlines to focus attention
on the final remaining tasks, with a series of 3 alphas prior to the
first beta release where each alpha release comes approximately every 3
weeks. We can have some flexibility to adjust this timetable if we think
it is necessary (such as by including an additional alpha release if
required).

Please let me know your thoughts. This would probably need to go to an
OMC vote to get approved.

Matt