clarify possible instances of zeebe rollback #4064
Conversation
christinaausley
added
component:zeebe
christinaausley
requested review from
akeller,
lenaschoenburg and
conceptualshark
| @@ -163,6 +163,10 @@ If the error is caused by `Cannot upgrade to or from a pre-release version`, Zee | |||
| This is not permitted because pre-release versions such as alpha releases are considered unstable and do not guarantee compatibility with any other version. | |||
| If you attempted to update from a normal version to a pre-release version, you can roll back to the previous normal version. | |||
|
|
|||
| :::note | |||
| While in most instances version rollbacks are not supported, in this particular use case a version rollback is possible. | |||
There was a problem hiding this comment.
| While in most instances version rollbacks are not supported, in this particular use case a version rollback is possible. | |
| While in most instances version rollbacks are not supported, in this particular use case a version rollback of Zeebe is possible because the "new" version never became active, thanks to the safety check. |
There was a problem hiding this comment.
I'm not sure the extra explanation adds a lot here. We don't otherwise talk about what the safety checks or doing, and can possibly introduce new points of confusion re: "new" vs "old" instead of clarifying. If we really think our developers need this info, I'd suggest something like:
..a version rollback of Zeebe is possible, as the included safety checks prevented the pre-release version from becoming active.
There was a problem hiding this comment.
I'd keep the addition of "Zeebe" then because rollback of the other applications might not be possible.
There was a problem hiding this comment.
Updated in latest commit -- let me know what you think.
| @@ -163,6 +163,10 @@ If the error is caused by `Cannot upgrade to or from a pre-release version`, Zee | |||
| This is not permitted because pre-release versions such as alpha releases are considered unstable and do not guarantee compatibility with any other version. | |||
| If you attempted to update from a normal version to a pre-release version, you can roll back to the previous normal version. | |||
|
|
|||
| :::note | |||
| While in most instances version rollbacks are not supported, in this particular use case a version rollback is possible. | |||
There was a problem hiding this comment.
I'm not sure the extra explanation adds a lot here. We don't otherwise talk about what the safety checks or doing, and can possibly introduce new points of confusion re: "new" vs "old" instead of clarifying. If we really think our developers need this info, I'd suggest something like:
..a version rollback of Zeebe is possible, as the included safety checks prevented the pre-release version from becoming active.
Description
Closes https://github.com/camunda/developer-experience/issues/345.
Clarifying unique instances of rollback.
When should this change go live?
holdlabel or convert to draft PR)PR Checklist
/versioned_docsdirectory./docsdirectory (aka/next/).