Readjusting the version numbers #2068
Conversation
| @@ -153,7 +153,7 @@ You can select a username/password account to perform automatic Tentacle updates | |||
| ## Recover from communication errors with Tentacle \{#MachinePolicies-Recoverfromcommunicationerrorswithtentacle} | |||
|
|
|||
| :::div{.hint} | |||
| Recovering from communication errors with Tentacle is available to **Cloud** customers from **Octopus 2023.3** onwards and will be made available to self-hosted customers in a future release. | |||
| Recovering from communication errors with Tentacle is available from **Octopus 2023.4** onwards. | |||
There was a problem hiding this comment.
Now that we know 2023.4 is the version, let's lock that in.
Also, everyone in Cloud has RPC retries now. So it felt strange to distinguish them here. If a Cloud customer looks at their version, they will see it's >= 2023.4.
| The audit log retention functionality was gradually made available to **Cloud** customers from **Octopus 2023.1** onwards. | ||
|
|
||
| Audit log retention will be made available to self-hosted customers later in 2023. However, from **Octopus 2022.3** onwards, self-hosted customers will be able to change the **Event retention days** configuration, allowing you to adjust to your preferred retention period prior to retention archiving audit logs. | ||
| The audit log retention functionality is available from **Octopus 2023.3** onwards. |
There was a problem hiding this comment.
Having done the fix to RPC retries, I was reminded that we do similar version distinctions in event retention.
Applying the same logic, I felt that it has been around for a while now, and didn't need as much fan-fair now.
There was a problem hiding this comment.
I'm pretty sure this became available to the public in 2023.3. The feature toggle was removed then, so I believe that's good evidence 😁
|
This pull request has been linked to Shortcut Story #62820: After 2023.4 update public docs with the right version number. |
[sc-62820]
Updating the version numbers in our docs to be up-to-date for the RPC retries and Event Retention features.