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.
37 topic: For change requests which target both the master and the
38 OpenSSL_1_1_1-stable branch, the following procedure should be followed:
39 - First, a pull request needs to be opened against the master branch for
40 discussion. Only after that pull request has received the necessary
41 amount of approvals, a separate pull request can be opened against the
42 OpenSSL_1_1_1-stable branch.
43 - A separate pull request against the OpenSSL_1_1_1-stable branch is
44 required. This holds - contrary to common practice - even if the change
45 can be cherry-picked without conflicts from the master branch. The only
46 exception from this rule are changes which are considered 'CLA: trivial',
47 like e.g. typographical fixes.
48 Proposed by Matt Caswell
67 topic: Accept and merge #11577.
68 comment: #11577 reduces the maximum length of TLS labels.
69 It also breaks standards compliance.
83 Kurt [-1] # 2020-06-09
88 topic: Keep FIPS_mode() as emulated by EVP_default_properties_is_fips_enabled(NULL)
89 Proposed by Tomas Mraz
107 topic: approve PR#8300 statem: fix the alert sent for too large messages
108 Proposed by Tim Hudson