VOTE: Approve the 3.5 source as ready for final release

[mattcaswell]

Topic: OTC sign off the 3.5 source as ready for final release
Proposed by: Matt Caswell
Issue link: https://github.com/openssl/technical-policies/issues/112
Public: yes
Opened: 2025-04-04
Closed: YYY-MM-DD
Accepted:  yes/no  (for: X, against: Y, abstained: Z, not voted: W)

  Dmitry     [  ]
  Matt       [+1]
  Tim        [  ]
  Hugo       [  ]
  Richard    [  ]
  Shane      [  ]
  Tomas      [  ]
  Kurt       [  ]
  Pauli      [  ]
  Nicola     [  ]

[mattcaswell]

For background this is my assessment of the release readiness checklist:

All issues triaged as regressions on the development branch from which the release is to be done must have a milestone assigned. Regressions are considered from the previous stable release series.

There are no issues marked as a regression that were introduced in the 3.5 release.

All issues or pull requests with the milestone for the release are closed.

There are 3 currently open issues against the release milestone. All of them are minor issues and they are already in "approval done" and we expect them to merge over the weekend.

openssl/openssl#27265
openssl/openssl#27264
openssl/openssl#27258

There are no outstanding untriaged Coverity issues.

Our Coverity instance is currently broken. Therefore there aren't any untriaged Coverity issues :-)

I don't believe this problem should delay the 3.5 release.

Coveralls coverage has not decreased overall from the previous release from the particular development branch.

Coverage on tip of 3.4 branch: 67.899%
Coverage on tip of 3.5 branch: 68.264%

So coverage has increased since the last release by 0.365%

The CI must pass on the tip of the development branch before the release commits are added to the tree, including the daily CI builds.

The CI is currently green on the tip of the 3.5 branch:

https://github.com/openssl/openssl/actions?query=branch%3Aopenssl-3.5

The tree must be frozen for at least 7 days. No changes apart from regression or security fixes should be merged during the freeze.

The tree was frozen on 3rd April - so 5 days before the release. Technically this is therefore not met. But I see no reason to delay the release because of this.

For 2 days before the release there should be no changes to ensure the daily CI builds run on the development tree tip.

We aren't aware of any changes that would be required.

The OTC should explicitly approve that the source is ready for a release with a vote.

This vote

[beldmit]

+1

[t-j-h]

+1

[kroeckx]

+1

[t8m]

+1

[romen]

+1

[paulidale]

+1

[levitte]

+1

[slontis]

+1

[mattcaswell]

The vote is now closed. It passed:

Accepted:  yes  (for: 9, against: 0, abstained: 0, not voted: 1)

  Dmitry     [+1]
  Matt       [+1]
  Tim        [+1]
  Hugo       [  ]
  Richard    [+1]
  Shane      [+1]
  Tomas      [+1]
  Kurt       [+1]
  Pauli      [+1]
  Nicola     [+1]