docs(releases): Clarify behavior for "Resolved in next release" (gets…

…entry#12112) * Clarify resolvedin next release * Update docs/product/releases/index.mdx Co-authored-by: Armen Zambrano G. <[email protected]> * Update docs/product/releases/index.mdx Co-authored-by: Liza Mock <[email protected]> --------- Co-authored-by: Armen Zambrano G. <[email protected]> Co-authored-by: Liza Mock <[email protected]>
oil-bleach-re-el-idited · Dec 12, 2024 · dbd5de1 · dbd5de1
1 parent df510ba
commit dbd5de1
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/docs/product/releases/index.mdx b/docs/product/releases/index.mdx
@@ -72,7 +72,7 @@ The "Resolved in the current release" option records the current release that's
 
 ### Resolved in the Next Release
 
-The "Resolved in the next release" option works in a similar way to resolved in the current release. But because we can't record the resolution version since it hasn't been created yet, we record the current release version and update it when a newer release is created.
+The "Resolved in the next release" option works like resolving in the current release, but since the next release doesn’t exist yet, we record the latest version where the issue was seen. This updates automatically when a new release is created. For semantic versioning, the issue is resolved in the next newest of all current versions.
 
 ### Resolved in a Commit