v3/__ftp://ftp.openssl.org/source/__;!!GqivPVa7Brio!KZB-yqnb-lavPS0QU0YMDCJHPWYVDZTvtki0jN4zOd40AGRcKabolTvarW_pL9OONQ$>
>
>The distribution file name is:
>
> o openssl-3.0.0-alpha1.tar.gz
> Size: 9530120
> SHA1 checksum: 4db145d3d9c9d7bfaa7b2a1fe1670f7a3781bb0
FTP mirrors under
>https://www.openssl.org/source/mirror.html):
>
> * https://www.openssl.org/source/
> * ftp://ftp.openssl.org/source/
>
>The distribution file name is:
>
> o openssl-3.0.0-alpha1.tar.gz
&
* Windows 10 x64
* GCC 8.3.0 x86_64
$ openssl version -a
OpenSSL 3.0.0-alpha1 "23 Apr 2020" (Library: OpenSSL 3.0.0-alpha1 "23 Apr 2020")
built on: Fri Apr 24 18:14:53 2020 UTC
platform: mingw64
options: bn(64,64)
compiler: /mingw/bin/gcc.exe -m64 -DWINVER=0x0501 -
ist of required things for alpha 1 are done, it does seem
>> appropriate. I know of a couple things that would be bug reports against
>> an alpha1 if produced right now, but ... what is an alpha for, if not to
>> trigger people to look and file bug reports? :)
>
> I've
/
The distribution file name is:
o openssl-3.0.0-alpha1.tar.gz
Size: 9530120
SHA1 checksum: 4db145d3d9c9d7bfaa7b2a1fe1670f7a3781bb06
SHA256 checksum:
9d5be9122194ad1d649254de5e72afd329252f134791389d0cef627b18ed9a57
The checksums were calculated using the following
nking that we will do the alpha 1 release on Thursday this
>> week. That would imply a repo freeze tomorrow.
>>
>> Thoughts/opinions/objections to this proposal?
>
> Given that the list of required things for alpha 1 are done, it does seem
> appropriate. I know of a couple thin
. That would imply a repo freeze tomorrow.
>
> Thoughts/opinions/objections to this proposal?
Given that the list of required things for alpha 1 are done, it does seem
appropriate. I know of a couple things that would be bug reports against
an alpha1 if produced right now, but ..
The 3.0 developers met via conference call this morning. All the
functionality that we had planned for alpha 1 has now been merged, so we
are now thinking that we will do the alpha 1 release on Thursday this
week. That would imply a repo freeze tomorrow.
Thoughts/opinions/objections to this
Please see attached for what I believe is the critical path as well as
the key dependencies for Alpha 1. Please let me know of any errors or
omissions.
Matt
Yesterday a number of us had a teleconference to update our task
tracking for the 3.0 release. The current spreadsheet gives us the
following dates for the various alpha/beta releases:
Alpha1: 2020-04-15
Alpha2: 2020-05-04
Alpha3: 2020-06-10
Beta1: 2020-06-12
Comparing this to the official
10 matches
Mail list logo