Re: [openssl-project] Current votes FYI
On 29/05/18 06:45, Dr. Matthias St. Pierre wrote: >> VOTE: 1.1.1 beta release schedule changed so that the next two beta releases >> are now 29th May, 19 June and we will re-review release readiness after >> that. We will also ensure that there is at least one beta release post >> TLS-1.3 RFC publication prior to the final release. > > Note: I just had a look at https://www.openssl.org/policies/releasestrat.html > because I recalled that a beta release was scheduled for today and noticed > that the beta release plan has not been updated to reflect your last vote. > I thought it had been updated! So, https://github.com/openssl/web/pull/55 P.S. Ah! It *was* updated and then the change was reverted! ___ openssl-project mailing list openssl-project@openssl.org https://mta.openssl.org/mailman/listinfo/openssl-project
Re: [openssl-project] Current votes FYI
> VOTE: 1.1.1 beta release schedule changed so that the next two beta releases > are now 29th May, 19 June and we will re-review release readiness after that. > We will also ensure that there is at least one beta release post TLS-1.3 RFC > publication prior to the final release. Note: I just had a look at https://www.openssl.org/policies/releasestrat.html because I recalled that a beta release was scheduled for today and noticed that the beta release plan has not been updated to reflect your last vote. Matthias ___ openssl-project mailing list openssl-project@openssl.org https://mta.openssl.org/mailman/listinfo/openssl-project
Re: [openssl-project] Current votes FYI
Dang, you’re right.
I’ll re-run the vote. But for now I reverted the website commit.
From: Tim Hudson
Reply-To: "openssl-project@openssl.org"
Date: Wednesday, May 23, 2018 at 5:00 PM
To: "openssl-project@openssl.org"
Subject: Re: [openssl-project] Current votes FYI
No that vote does not pass. All votes require participation by a majority of
active members. Failure to have a majority participation causes a vote to fail.
With only three out of eight members voting this vote simply did not pass.
Tim.
On Thu, 24 May 2018, 12:59 am Salz, Rich,
mailto:rs...@akamai.com>> wrote:
Another update
VOTE: Remove the second paragraph ("Binary compatibility...improve security")
from the release strategy.
+1: 2
0: 1
-1: 0
No vote: 5
The vote passed.
___
openssl-project mailing list
openssl-project@openssl.org<mailto:openssl-project@openssl.org>
https://mta.openssl.org/mailman/listinfo/openssl-project<https://urldefense.proofpoint.com/v2/url?u=https-3A__mta.openssl.org_mailman_listinfo_openssl-2Dproject&d=DwMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=4LM0GbR0h9Fvx86FtsKI-w&m=nzvJc3ymtWOe43oeRGdwI3GgaAQqIFFLzpsIxvWJ4Gc&s=xWgXumtW5Lnbf9inmYXMQFmVpApZyIIR8BuMkxRICZw&e=>
___
openssl-project mailing list
openssl-project@openssl.org
https://mta.openssl.org/mailman/listinfo/openssl-project
Re: [openssl-project] Current votes FYI
No that vote does not pass. All votes require participation by a majority
of active members. Failure to have a majority participation causes a vote
to fail.
With only three out of eight members voting this vote simply did not pass.
Tim.
On Thu, 24 May 2018, 12:59 am Salz, Rich, wrote:
> Another update
>
> VOTE: Remove the second paragraph ("Binary compatibility...improve
> security")
> from the release strategy.
>
> +1: 2
> 0: 1
> -1: 0
> No vote: 5
>
> The vote passed.
>
>
> ___
> 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
Re: [openssl-project] Current votes FYI
Another update
VOTE: Remove the second paragraph ("Binary compatibility...improve security")
from the release strategy.
+1: 2
0: 1
-1: 0
No vote: 5
The vote passed.
___
openssl-project mailing list
openssl-project@openssl.org
https://mta.openssl.org/mailman/listinfo/openssl-project
Re: [openssl-project] Current votes FYI
FYI, all of these votes are now closed. The final vote results are inserted below. On 07/05/18 02:37, Salz, Rich wrote: > VOTE: openssl-web and tools repositories shall be under the same review > policy as per the openssl repository where the reviewers are OMC members +1: 5 0: 1 -1: 1 No vote: 1 The vote passed. > VOTE: That we remove "We strongly believe that the right to advance > patches/info should not be based in any way on paid membership to some > forum. You cannot pay us to get security patches in advance" from the > security policy and Mark posts a blog entry to explain the change > including that we have no current such service. +1: 4 0: 2 -1: 1 No vote: 1 The vote passed. > VOTE: 1.1.1 beta release schedule changed so that the next two beta > releases are now 29th May, 19 June and we will re-review release > readiness after that. We will also ensure that there is at least one > beta release post TLS-1.3 RFC publication prior to the final release. +1: 7 0: 0 -1: 0 No vote: 1 The vote passed. > VOTE: Remove the entire "Forthcoming Features" section from the Roadmap > Policy and open github issues for those items listed which have not yet > been completed and do not currently have issues raised or PR submitted. +1: 4 0: 3 -1: 0 No vote: 1 The vote passed. > VOTE: We don't intend to be involved in adding any additional platforms > to the OpenSSL FIPS validation; instead we will work to enable other > parties to meet this need. +1: 5 0: 2 -1: 0 No vote: 1 The vote passed. > VOTE: The next LTS release will be 1.1.1 and the LTS expiry date for > 1.0.2 will not be changed. +1: 7 0: 0 -1: 0 No vote: 1 The vote passed. ___ openssl-project mailing list openssl-project@openssl.org https://mta.openssl.org/mailman/listinfo/openssl-project
[openssl-project] Current votes FYI
Greetings OpenSSL folks! The OMC met this past weekend. Much was accomplished. Per our policy, we’re telling the project that the following votes are now active among the OMC. As the votes are concluded, more information (blog posts, website updates, whatever’s appropriate) will be made available. VOTE: openssl-web and tools repositories shall be under the same review policy as per the openssl repository where the reviewers are OMC members VOTE: That we remove "We strongly believe that the right to advance patches/info should not be based in any way on paid membership to some forum. You cannot pay us to get security patches in advance" from the security policy and Mark posts a blog entry to explain the change including that we have no current such service. VOTE: 1.1.1 beta release schedule changed so that the next two beta releases are now 29th May, 19 June and we will re-review release readiness after that. We will also ensure that there is at least one beta release post TLS-1.3 RFC publication prior to the final release. VOTE: Remove the entire "Forthcoming Features" section from the Roadmap Policy and open github issues for those items listed which have not yet been completed and do not currently have issues raised or PR submitted. VOTE: We don't intend to be involved in adding any additional platforms to the OpenSSL FIPS validation; instead we will work to enable other parties to meet this need. VOTE: The next LTS release will be 1.1.1 and the LTS expiry date for 1.0.2 will not be changed. ___ openssl-project mailing list openssl-project@openssl.org https://mta.openssl.org/mailman/listinfo/openssl-project
