8.7-alpha5 release notes

[conceptualshark]

Description

Includes notes or placeholders for alpha5 labeled epics.

When should this change go live?

• This is a bug fix, security concern, or something that needs urgent release support. (add bug or support label)
• This is already available but undocumented and should be released within a week. (add available & undocumented label)
• This is on a specific schedule and the assignee will coordinate a release with the DevEx team. (create draft PR and/or add hold label)
• This is part of a scheduled alpha or minor. (add alpha or minor label)
• There is no urgency with this change (add low prio label)

PR Checklist

• My changes are for an upcoming minor release and:
  • are in the /docs directory (version 8.8).
  • are in the /versioned_docs/version-8.7/ directory (version 8.7).
• My changes are for an already released minor and are in a /versioned_docs directory.

• I added a DRI, team, or delegate as a reviewer for technical accuracy and grammar/style:
  • Engineering team review
  • Technical writer review via @camunda/tech-writers unless working with an embedded writer.

[github-actions]

👋 🤖 🤔 Hello, @akeller! Did you make your changes in all the right places?

These files were changed only in docs/. You might want to duplicate these changes in versioned_docs/version-8.6/.

• docs/reference/release-notes/870.md

These files were changed only in versioned_docs/version-8.7/. You might want to duplicate these changes in versioned_docs/version-8.6/.

• versioned_docs/version-8.7/reference/release-notes/870.md

You may have done this intentionally, but we wanted to point it out in case you didn't. You can read more about the versioning within our docs in our documentation guidelines.

[akeller]

I didn't see Document Handling in here yet, but the epic is on an incremental delivery path. @christinaausley has an open docs PR. Can we add something about what is specifically being delivered this increment?

[mesellings]

Great work getting this together - approved with lots of non-blocking comments - I wasn't sure if you wanted me to go through and rewrite any of these entries as I think some can be improved - let me know if you would like me to? One more thing is whether to organise these alphabetically - I'm not sure if there is any logical grouping/ordering of items I can work out? By front-loading and ordering alphabetically it at least allows easier scanning for the items a user might want to know about? 👏 🚀

[conceptualshark]

@mesellings Apologies for marking your comments as resolve wholesale, but I used it to check off my updates - they should all be incorporated or adjusted! Thank you for taking a look.

[akeller]

@conceptualshark this PR didn't add the new section to the TOC at the top of the page. Should it be there? (CC @christinaausley as the reviewer of the PR)

Additionally, I'm going to (hopefully) merge in #5179, which will add another section, but I did add it to the TOC.

Can you make sure this is consistent/cleaned up?

[conceptualshark]

Should we add reviewing the Announcements for consistency to the release manager tasks? I can make a separate PR to reconcile them, but hadn't been tracking changes there otherwise.

[akeller]

Approving to merge, but I did not double check the epics in listed here against the Product Hub. I would need to do that in a follow up.

[github-actions]

🧹 Preview environment for this PR has been torn down.