Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update migration-journey.md #5170

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

jonathanlukas
Copy link
Contributor

Description

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.

@jonathanlukas jonathanlukas added the hold This issue is parked, do not merge. label Mar 6, 2025
@jonathanlukas jonathanlukas requested a review from aletutto March 6, 2025 13:55
@jonathanlukas jonathanlukas self-assigned this Mar 6, 2025
Copy link
Contributor

github-actions bot commented Mar 6, 2025

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

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

  • versioned_docs/version-8.6/guides/migrating-from-camunda-7/migration-journey.md
These files were changed only in versioned_docs/version-8.6/. You might want to duplicate these changes in versioned_docs/version-8.7/.
  • versioned_docs/version-8.6/guides/migrating-from-camunda-7/migration-journey.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.

@@ -120,6 +126,8 @@ Furthermore, you can use the [migration tooling](./migration-tooling.md) and rel

To run any solution on Camunda 8, you must have a running Camunda 8 installation.

// TODO mention that Saas is also a "running installation" in that sense
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[all.glossary] Inconsistent spelling detected. Use SaaS instead of Saas. Review the WCoE glossary - https://confluence.camunda.com/x/b5RZBw .

@@ -82,6 +82,8 @@ Migrating to Camunda 8 gives you additional advantages, which might raise priori
- You need performance at scale and/or improved resilience.
- You need certain features that can only be found in Camunda 8 (for example, BPMN message buffering, improved multi-instance handling, the new Connectors framework, RPA, IDP, or the improved collaboration features in Web Modeler).

// TODO: Link to conceptual differences
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[prettier] reported by reviewdog 🐶

Suggested change
// TODO: Link to conceptual differences
// TODO: Link to conceptual differences

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hold This issue is parked, do not merge.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant