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

Plausibility check of new Optimize 7 docs #4797

Open
Tracked by #4716
mboskamp opened this issue Nov 15, 2024 · 1 comment
Open
Tracked by #4716

Plausibility check of new Optimize 7 docs #4797

mboskamp opened this issue Nov 15, 2024 · 1 comment
Assignees
Labels
type:subtask Issues that are subtasks of another issue. Must always be part of the breakdown of the parent issue.

Comments

@mboskamp
Copy link
Member

mboskamp commented Nov 15, 2024

Acceptance Criteria (Required on creation)

  • Skim through the changes/additions that were migrated to the Optimize 7 docs in this ticket and flag anything incorrect or worth changing.
  • Skim through the published docs and flag if you find anything that is missing and noteworthy to move as well.

Hints

The following branches have been updated:

Links

Breakdown

Pull Requests

No tasks being tracked yet.
@mboskamp mboskamp added the type:subtask Issues that are subtasks of another issue. Must always be part of the breakdown of the parent issue. label Nov 15, 2024
@mboskamp mboskamp assigned PHWaechtler and unassigned mboskamp Dec 2, 2024
@mboskamp
Copy link
Member Author

mboskamp commented Dec 2, 2024

Hey @PHWaechtler, do you mind checking the content I migrated for the docs for any inconsistencies?

You can find out what was migrated from this ticket.
I released 3.14 as latest and develop, so the content there is identical.
3.11-3.13 should only have the documentation for things that were added for those versions. Again, see the above ticket for what was added.

Please also take a look at the most important parts (supported environments, configuration properties, update guides). The base version I used was 3.8. Then I migrated the content from the respective version branch from docs.camunda.io. There might be stuff that I missed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:subtask Issues that are subtasks of another issue. Must always be part of the breakdown of the parent issue.
Projects
None yet
Development

No branches or pull requests

2 participants