PR for SRVLOGIC-752: Update Release Notes content for Serverless Logic 1.37

[kaldesai]

Affected versions: serverless-docs-1.37

Tracking JIRA: https://issues.redhat.com/browse/SRVLOGIC-752

Doc preview:

• Serverless Logic 1.37 release notes

Reviews:

• QE has approved this change.

• SME has approved this change.

• Peer has approved this change.

[openshift-ci-robot]

@kaldesai: This pull request references SRVLOGIC-752 which is a valid jira issue.

In response to this:

Affected versions: serverless-docs-1.37

Tracking JIRA: https://issues.redhat.com/browse/SRVLOGIC-752

Doc preview:

• Serverless Logic 1.37 release notes

Reviews:

• QE has approved this change.

• SME has approved this change.

• Peer has approved this change.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@kaldesai: This pull request references SRVLOGIC-752 which is a valid jira issue.

In response to this:

Affected versions: serverless-docs-1.37

Tracking JIRA: https://issues.redhat.com/browse/SRVLOGIC-752

Doc preview:

• Serverless Logic 1.37 release notes

Reviews:

• QE has approved this change.

• SME has approved this change.

• Peer has approved this change.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[kaldesai]

/label serverless

[kaldesai]

/retest

[kaldesai]

/retest

[kaldesai]

/retest-required

[kaldesai]

/test validate-asciidoc

[openshift-ci]

@kaldesai: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/validate-asciidoc	e05afcc	link	true	/test validate-asciidoc

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.