1 # A record of formal votes in reverse chronological order.
3 # To vote, add one of the following entries next to your name:
5 # [+1] I vote in favour of the proposal
6 # [ 0] I abstain from the vote
7 # [-1] I vote against the proposal
9 # If you are abstaining, you can indicate a tendency as follows:
11 # [+0] I abstain but with a slight lean towards a vote in favour
12 # [ 0] I abstain with no stated preference
13 # [-0] I abstain but with a slight lean towards a vote against
15 # A template for voting (alphabetical by surname) follows.
23 accepted: yes/no (+X, -Y)
38 topic: Rename OSSL_SERIALIZER / OSSL_DESERIALIZER to OSSL_ENCODER / OSSL_DECODER
40 The rationale is that it makes things easier on programmers
41 (encode / decode is easier to write than serialize / deserialize),
42 and also avoids disputes on what is and isn't serialization.
44 Associated issues and PRs: #12455, #12659 and #12660
51 accepted: yes/no (+X, -Y)
66 topic: Rename OPENSSL_CTX to OSSL_LIB_CTX (as proposed by pull request #12621)
68 The main rationale behind this change is consistency, because many of the new
69 OpenSSL 3.0 types have an OSSL_ prefix, and OPENSSL_CTX is a notable exception.
70 More details can be found in the description and thread of pull request #12621.
72 There was a discussion on openssl-committers ('Rename OPENSSL_CTX to OSSL_WHAT?')
73 and an initial poll on doodle about the favourite replacements for OPENSSL_CTX
74 (https://doodle.com/poll/drku9ziwvkp6tw25).
76 Proposed by Matthias St. Pierre
80 accepted: yes/no (+X, -Y)
95 topic: For change requests which target both the master and the
96 OpenSSL_1_1_1-stable branch, the following procedure should be followed:
97 - First, a pull request needs to be opened against the master branch for
98 discussion. Only after that pull request has received the necessary
99 amount of approvals, a separate pull request can be opened against the
100 OpenSSL_1_1_1-stable branch.
101 - A separate pull request against the OpenSSL_1_1_1-stable branch is
102 required. This holds - contrary to common practice - even if the change
103 can be cherry-picked without conflicts from the master branch. The only
104 exception from this rule are changes which are considered 'CLA: trivial',
105 like e.g. typographical fixes.
106 Proposed by Matt Caswell
110 accepted: no (+4, -4)
126 topic: Accept and merge #11577.
127 comment: #11577 reduces the maximum length of TLS labels.
128 It also breaks standards compliance.
133 accepted: no (+0, -8)
143 Kurt [-1] # 2020-06-09
148 topic: Keep FIPS_mode() as emulated by EVP_default_properties_is_fips_enabled(NULL)
149 Proposed by Tomas Mraz
153 accepted: no (+2, -5)
168 topic: approve PR#8300 statem: fix the alert sent for too large messages
169 Proposed by Tim Hudson
173 accepted: no (+1, -4)