7.17.14 Release notes

[nastasha-solomon]

Description

Generate the 7.17.14 release notes and publish them before or on the release day, which is October 10, 2023.

Milestone dates:

• FF: October 4, 2023
• BC: October 6, 2023
• Release: October 10, 2023

Steps

1. Create a new branch:
   a. From the CLI, run git checkout 7.17 to checkout the 7.17 branch. Can also checkout the branch using GH Desktop.
   b. Run git fetch origin to retrieve the latest version of the 7.17 branch.
   c. Run git pull to pull down the latest changes in the main branch.
   d. Run git checkout -b issue-XXX-7.17.14-rn to create a new local branch.
2. Open the Security docs project in your text editor (VS Code).
3. Expand the release-notes folder the open the 7.17.asciidoc file.
4. At the top of the file, create a new section for the 7.17.14 release notes, for example:

[discrete]
[[release-notes-7.17.14]]
=== 7.17.14

[discrete]
[[bug-fixes-7.17.14]]
==== Bug fixes and enhancements
* TBD

5. Open the release-notes.asciidoc file and insert a link to the 7.17.14 release notes, for example: <<release-notes-7.17.14, {elastic-sec} version 7.17.14>>
6. Save your changes.
7. Commit and push your changes. Can do all of this from GH Desktop or from the CLI. Steps for CLI:
   a. Run git add --all to add changes from all tracked and untracked files.
   b. Run git commit -m "A brief description of your change" to commit your changes.
   c. Run git push to create a remote branch and push your changes it. If the branch doesn’t already exist in the remote repo, it is automatically created.
8. Open a PR in GH to start reviewing your changes. Remember to choose the 7.17 branch when specifying which branch the PR should be merged into. DO NOT merge the PR with main.

Notes:

• @nastasha-solomon to confirm with @roxana-gheorghe that there are no Endpoint PRs that need to be release-noted for 7.7.14.
• If you add the PR to the Endpoint feature/bug/known issue, use the hardcoded URL to create the reference link. Here is an example.
• ResponseOps features for cases, connectors, and alerts are always doc'd in the Kibana release notes unless they are Security-specific features. This is also the case for Osquery feature and enhancements.
• There is no need to add additional version labels to the PR. The PR will not need to be backported.

[nastasha-solomon]

Confirmed with @roxana-gheorghe that there are no PRs that need to be release-noted for this release.

[nastasha-solomon]

Closed #4010.