Alpha2 release notes

[akeller]

Description

All known epics & features have been added, including internal links (public or private, as comments).

Note - some links to new docs generated for new epics are not live yet.

When should this change go live?

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

PR Checklist

• My changes are for an already released minor and are in /versioned_docs directory.
• My changes are for the next minor and are in /docs directory (aka /next/).

• My changes require an Engineering review, and I've assigned the Engineering DRI or delegate.
• My changes require a technical writer review, and I've assigned @christinaausley as a reviewer.

[github-actions]

👋 🤖 🤔 Hello! 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.5/.

• docs/reference/release-notes/860.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]

@camunda/tech-writers, I've marked this as ready for review, but have not done any editing myself. We do not yet have a standard format or "style" for release notes, but we can discuss this as a team.

The top two epics/features on the PR were content I generated from the descriptions, value prop, and implementation tickets. We'll need @sbuettner or a delegate to review those.

[sbuettner]

Great @akeller what do you think about grouping and/or ordering release notes by component?

[akeller]

Great @akeller what do you think about grouping and/or ordering release notes by component?

@sbuettner I'll consider this in another iteration. For now, I want to focus on surfacing the right items in the release notes. Since alphas are generally smaller, I'm hoping to get to this for the next minor.

[sbuettner]

Alright, I thought it would be nice to see them grouped together somehow so people can navigate the release notes more easily. Thanks for your support!