[web] master update
The branch master has been updated via 03e84f49907d92dda63a9360090781fc8ed96910 (commit) from 95646d33a713dd67de6aef668fb717aca07fa11a (commit) - Log - commit 03e84f49907d92dda63a9360090781fc8ed96910 Author: Matt Caswell Date: Wed Oct 13 11:24:10 2021 +0100 Update the platform policy as per OMC decision Reviewed-by: Tim Hudson (Merged from https://github.com/openssl/web/pull/266) --- Summary of changes: policies/platformpolicy.html | 247 +++ 1 file changed, 202 insertions(+), 45 deletions(-) diff --git a/policies/platformpolicy.html b/policies/platformpolicy.html index 24b4829..cdf2db4 100644 --- a/policies/platformpolicy.html +++ b/policies/platformpolicy.html @@ -7,59 +7,216 @@ - - - - Platform Policy - + + + + Platform Policy + + + Platforms are classified as "primary", "secondary", "community" + and "unadopted". Support for a new platform should only be + added if it is being adopted as a primary, secondary or + community platform. + +Primary + + Definition: A platform that is regularly tested + through project CI on a project owned and managed system + - + New Pull Requests (PRs) should not be merged unless the + primary platforms are showing as "green" in CI. If the CI + breaks for a branch (such as for a stable version or master) + then it should be fixed as a priority. + +Secondary + + Definition: A platform that is regularly tested + through project CI on a system that is not owned or managed by + the project. At least one project committer must have access + to the system and be able and willing to support it. - NOTE: Work In Progress + New Pull Requests (PRs) should avoid introducing new breaks to + CI in secondary platforms where possible but may still be + merged where a resolution is not easily achievable without + access to the platform. If the CI for a branch (such as for a + stable version or master) on a secondary platform breaks, then + a resolution should be sought as soon as is practically + possible and before a release is made from the branch. + +Community + + Definition: Platforms that one or more members of the + OpenSSL community have volunteered to support. May or may not + be in project CI. Members of the community providing support + do not have to be committers. - Each platform is classified as: - - Primary - - Target(s) on which the majority of OpenSSL - development occurs + Where a community platform is in project CI then new Pull + Requests (PRs) should avoid introducing new breaks to CI on + such platforms where possible but may still be merged where a + resolution is not easily achievable without access to the + platform. If the CI for a branch (such as for a + stable version or master) on a community platform breaks, then + an attempt should be made to contact the community maintainer + to request a fix. In the event that a community platform is + broken in CI for a protacted period then it may be dropped + from CI. - The current primary development platform is - Linux. - - Secondary - - Targets which at least one team member actively supports, or the - platform is covered by CI and at least one team member has access to - the platform. + If defects are raised that are specific to a community + platform then the community maintainer may be contacted to + help find a resolution. If a community maintainer is + unresponsive, or unable to provide fixes then the platform may + be moved to "unadopted". + +Unadopted + + Definition: Platforms that no one has volunteered to + support. +
[openssl] openssl-3.0 update
The branch openssl-3.0 has been updated via 2f98fd4b04bcb25fd7134c39ea4930c57615d4ea (commit) from 26d2016d5b81d78de90f075d630d38fe2badb84f (commit) - Log - commit 2f98fd4b04bcb25fd7134c39ea4930c57615d4ea Author: Matt Caswell Date: Thu Oct 14 17:04:16 2021 +0100 Fix the signature newctx documentation The documentation omitted the propq parameter Fixes #16755 Reviewed-by: Richard Levitte Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/16836) (cherry picked from commit 5fdc95e443b4d62a3d1f7094ae6d6ae4682b77e0) --- Summary of changes: doc/man7/provider-signature.pod | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/doc/man7/provider-signature.pod b/doc/man7/provider-signature.pod index a299d43cc5..9d4df86fd6 100644 --- a/doc/man7/provider-signature.pod +++ b/doc/man7/provider-signature.pod @@ -18,7 +18,7 @@ provider-signature - The signature library E-E provider functions */ /* Context management */ - void *OSSL_FUNC_signature_newctx(void *provctx); + void *OSSL_FUNC_signature_newctx(void *provctx, const char *propq); void OSSL_FUNC_signature_freectx(void *ctx); void *OSSL_FUNC_signature_dupctx(void *ctx); @@ -104,7 +104,7 @@ function pointer from an B element named B. For example, the "function" OSSL_FUNC_signature_newctx() has these: - typedef void *(OSSL_FUNC_signature_newctx_fn)(void *provctx); + typedef void *(OSSL_FUNC_signature_newctx_fn)(void *provctx, const char *propq); static ossl_inline OSSL_FUNC_signature_newctx_fn OSSL_FUNC_signature_newctx(const OSSL_DISPATCH *opf); @@ -183,7 +183,9 @@ structure for holding context information during a signature operation. A pointer to this context will be passed back in a number of the other signature operation function calls. The parameter I is the provider context generated during provider -initialisation (see L). +initialisation (see L). The I parameter is a property query +string that may be (optionally) used by the provider during any "fetches" that +it may perform (if it performs any). OSSL_FUNC_signature_freectx() is passed a pointer to the provider side signature context in the I parameter.
[openssl] master update
The branch master has been updated via 5fdc95e443b4d62a3d1f7094ae6d6ae4682b77e0 (commit) from fb0f65fff831d9294e34b6ef6f579c157db54b04 (commit) - Log - commit 5fdc95e443b4d62a3d1f7094ae6d6ae4682b77e0 Author: Matt Caswell Date: Thu Oct 14 17:04:16 2021 +0100 Fix the signature newctx documentation The documentation omitted the propq parameter Fixes #16755 Reviewed-by: Richard Levitte Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/16836) --- Summary of changes: doc/man7/provider-signature.pod | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/doc/man7/provider-signature.pod b/doc/man7/provider-signature.pod index a299d43cc5..9d4df86fd6 100644 --- a/doc/man7/provider-signature.pod +++ b/doc/man7/provider-signature.pod @@ -18,7 +18,7 @@ provider-signature - The signature library E-E provider functions */ /* Context management */ - void *OSSL_FUNC_signature_newctx(void *provctx); + void *OSSL_FUNC_signature_newctx(void *provctx, const char *propq); void OSSL_FUNC_signature_freectx(void *ctx); void *OSSL_FUNC_signature_dupctx(void *ctx); @@ -104,7 +104,7 @@ function pointer from an B element named B. For example, the "function" OSSL_FUNC_signature_newctx() has these: - typedef void *(OSSL_FUNC_signature_newctx_fn)(void *provctx); + typedef void *(OSSL_FUNC_signature_newctx_fn)(void *provctx, const char *propq); static ossl_inline OSSL_FUNC_signature_newctx_fn OSSL_FUNC_signature_newctx(const OSSL_DISPATCH *opf); @@ -183,7 +183,9 @@ structure for holding context information during a signature operation. A pointer to this context will be passed back in a number of the other signature operation function calls. The parameter I is the provider context generated during provider -initialisation (see L). +initialisation (see L). The I parameter is a property query +string that may be (optionally) used by the provider during any "fetches" that +it may perform (if it performs any). OSSL_FUNC_signature_freectx() is passed a pointer to the provider side signature context in the I parameter.
