docs(web-modeler): announce milestone to version renaming

[wollefitz]

Description

Part of https://github.com/camunda/web-modeler/issues/12551 and follow-up for #4868

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/).

• I added a redirect for a renamed or deleted page to the .htaccess file.

• 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 @camunda/tech-writers as a reviewer.

[akeller]

@wollefitz, is this labeled because it's already available in SaaS but will be in SM in alpha4? 🤔 maybe we need to discuss how to label things better for Web Modeler.

[wollefitz]

@wollefitz, is this labeled because it's already available in SaaS but will be in SM in alpha4?

Yes, exactly. In SaaS, we just continuously release the features of which most of them eventually will end up in SM.

🤔 maybe we need to discuss how to label things better for Web Modeler.

I think so, too. Until now, we always applied SaaS changes to next only which might be confusing for users looking for already available features in the latest stable version docs.

[wollefitz]

@camunda/tech-writers Just wanted to check in again on the status of this PR - do you think we can get it merged soon so that SaaS-users are already made aware of the naming changes within Web Modeler?

[christinaausley]

Made some formatting adjustments and added a few links here. One non-blocking comment. If you feel this would be helpful for users, I can certainly open an issue for it. If you don't feel users will struggle with this change, we can leave it as is for now.

[wollefitz]

With these changes, is it worth adding "versions (formerly milestones)" to any of the Web Modeler references for clarity? docs/components/modeler/web-modeler/process-application-versioning.md and docs/components/modeler/web-modeler/versions.md, for example.

I think it would be helpful to mention the former naming somewhere so that when using the search, you land on the new versions page 👍

Do you already have something in mind/would this be a small change or should we do it as a follow-up?

[christinaausley]

@wollefitz I added a note in two places in my latest commit -- WDYT?

[wollefitz]

Thanks for the adjustment, sounds good! Let's get this merged 🙂

[mesellings]

Lgtm - one very minor (non-blocking) wording change for simplicity/translation, but good to go without the change 👍 🚀

[wollefitz]

Lgtm - one very minor (non-blocking) wording change for simplicity/translation, but good to go without the change 👍 🚀

@mesellings I applied your suggestion but now need another approving review 🫠 After that I'll merge

[mesellings]

Lgtm! 🚀