Skip to content

Commit dbd5de1

Browse files
snigdhasarmenzglizokm
authored
docs(releases): Clarify behavior for "Resolved in next release" (#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]>
1 parent df510ba commit dbd5de1

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/product/releases/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ The "Resolved in the current release" option records the current release that's
7272

7373
### Resolved in the Next Release
7474

75-
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.
75+
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.
7676

7777
### Resolved in a Commit
7878

0 commit comments

Comments
 (0)