Text from the release strategy page should be reviewed

[mattcaswell]

The release strategy is currently available on the website here:

https://www.openssl.org/policies/releasestrat.html

There is information on:

• The versioning scheme
• Definitions of alpha/beta release and standard release criteria

We should consider whether any of the above text should be converted into a technical policy (either as-is or rewritten).

Other sections of that page are probably more OMC policy. I've created a proposal for those sections here:

openssl/general-policies#3

As noted in that PR, I've left out 2 bullets about stability that currently exist on the release strategy page. Specifically;

• No existing public interface can be modified except where changes are unlikely to break source compatibility or where structures are made opaque.
• When structures are made opaque, any newly required accessor macros or functions are added in a feature release of the extant LTS release and all supported intermediate successor releases.

We should consider whether any of this text should be incorporated into our stable release updates policy.

[mspncp]

Is this issue just stalled or completed?