From 362fa55106cf992ff91b53bc0e5f09b79f94f1f5 Mon Sep 17 00:00:00 2001 From: Snigdha Sharma Date: Thu, 12 Dec 2024 10:22:40 -0800 Subject: [PATCH 1/3] Clarify resolvedin next release --- docs/product/releases/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/product/releases/index.mdx b/docs/product/releases/index.mdx index 3fac0e4bb4268a..6b55b2795b40a6 100644 --- a/docs/product/releases/index.mdx +++ b/docs/product/releases/index.mdx @@ -66,7 +66,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 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 latest release version the group was seen in and update it when a newer release is created. ### Resolved in a Commit From 4aa74a1bc7692e5f5f84ceab7203bb9e99ed8795 Mon Sep 17 00:00:00 2001 From: Snigdha Sharma Date: Thu, 12 Dec 2024 10:52:11 -0800 Subject: [PATCH 2/3] Update docs/product/releases/index.mdx Co-authored-by: Armen Zambrano G. <44410+armenzg@users.noreply.github.com> --- docs/product/releases/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/product/releases/index.mdx b/docs/product/releases/index.mdx index 6b55b2795b40a6..3bbe27417003ee 100644 --- a/docs/product/releases/index.mdx +++ b/docs/product/releases/index.mdx @@ -66,7 +66,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 latest release version the group was seen in and update it when a newer release is created. +The "Resolved in the next release" option works similarly to resolving in the current release. But because we can't record the resolution version since it hasn't been created yet, we record the latest release version the group was seen in and update it when a newer release is created. When using semantic versioned releases, the group will be resolved with the next release which is greater than all existing ones. ### Resolved in a Commit From 05b304f121eebac13ff09f0cef9f2ce9150fe660 Mon Sep 17 00:00:00 2001 From: Snigdha Sharma Date: Thu, 12 Dec 2024 14:59:43 -0800 Subject: [PATCH 3/3] Update docs/product/releases/index.mdx Co-authored-by: Liza Mock --- docs/product/releases/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/product/releases/index.mdx b/docs/product/releases/index.mdx index 3bbe27417003ee..c4edad467cffee 100644 --- a/docs/product/releases/index.mdx +++ b/docs/product/releases/index.mdx @@ -66,7 +66,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 similarly to resolving in the current release. But because we can't record the resolution version since it hasn't been created yet, we record the latest release version the group was seen in and update it when a newer release is created. When using semantic versioned releases, the group will be resolved with the next release which is greater than all existing ones. +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