+1, in particular for doing a triple release: the 1.0.2 branch has accumulated a lot of substantial bugfixes.
(Personally, I am waiting on behalf of my company for Nicola's fix for the crash in FIPS mode https://github.com/openssl/openssl/commit/fff1da43be2236995cdf5ef2f3e2a51be232ba85) Matthias > -----Ursprüngliche Nachricht----- > Von: openssl-project <openssl-project-boun...@openssl.org> Im Auftrag von > Richard Levitte > Gesendet: Mittwoch, 14. November 2018 14:43 > An: openssl-project@openssl.org > Betreff: Re: [openssl-project] Release scheduling > > Only one thought: +1 > > Matt Caswell <m...@openssl.org> skrev: (14 november 2018 14:27:17 CET) > >There are now no open PRs/issues with the 1.1.1a milestone so I think > >we should > >go ahead and do a release. The question is when? I propose next Tuesday > >(20th), > >with releases of 1.1.0 and 1.0.2 on the same day. It's been a while > >since they > >last had releases so I think its worthwhile doing them at the same > >time. > > > >Thoughts? > > > >Matt > >_______________________________________________ > >openssl-project mailing list > >openssl-project@openssl.org > >https://mta.openssl.org/mailman/listinfo/openssl-project > > -- > Skickat från min Android-enhet med K-9 Mail. Ursäkta min fåordighet. > _______________________________________________ > 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
