id
stringlengths
21
21
kind
stringclasses
3 values
options
listlengths
2
6
target
listlengths
2
6
state
stringlengths
163
241
question
stringclasses
7 values
domain
stringclasses
1 value
family
stringclasses
1 value
source
stringclasses
1 value
v3_d6c10fc4aa16aa10_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0.01, 0.01, 0.04, 0.36, 0.55, 0.03 ]
A hotfix build is scheduled for the Friday freeze window; additionally introduces a new database index on a 2TB table. Context: in the payments repo, at the end of the fiscal period. Reported by the monitoring system.
Rate release readiness for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_1afc777bd3ffdb81_c
choice
[ "ship", "ship_with_monitoring", "hold", "rollback" ]
[ 0, 0.03, 0.72, 0.25 ]
A hotfix build changes 40% of the billing module; additionally shows a 9% regression in the p95 benchmark. Context: after a 3-week stabilization, during an external partner integration. Reported by the review queue.
Go/no-go for this scenario.
software_delivery
technical
yuri_v3
v3_519ee9a2da8a94b9_n
noul
[ "false", "true" ]
[ 0.71, 0.29 ]
The sdk release changes 40% of the billing module; additionally ships behind a feature flag at 5% traffic. Context: ahead of the audit, during the holiday freeze. Reported by the operator.
Is this scenario one where: the flag default is wrong?
software_delivery
technical
yuri_v3
v3_edbdfb05f96c3ce1_n
noul
[ "false", "true" ]
[ 0.33, 0.67 ]
A canary deploy has one blocking review comment unresolved; additionally modifies the auth middleware. Context: in the payments repo, during the morning shift. Reported by the review queue.
Is this scenario one where: the change needs a second reviewer?
software_delivery
technical
yuri_v3
v3_1709b8306cf82041_c
choice
[ "smoke", "full_regression", "targeted_suite", "extended_soak" ]
[ 0.02, 0.63, 0.31, 0.04 ]
The sdk release deletes a deprecated API with 3 known consumers; additionally passed the full canary matrix. Context: in the payments repo, while on-call rotation changed. Reported by the operator.
Test depth for this scenario.
software_delivery
technical
yuri_v3
v3_d80c94e8febf63dc_n
noul
[ "false", "true" ]
[ 0.94, 0.06 ]
The sdk release shows a 9% regression in the p95 benchmark; additionally passes unit tests but fails 2 integration tests. Context: ahead of the audit, during a scheduled maintenance window. Reported by the on-call engineer.
Is this scenario one where: this is safe to ship today?
software_delivery
technical
yuri_v3
v3_58e56ce78fdef5ba_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0, 0, 0.1414, 0.8182, 0.0404 ]
A hotfix build passes unit tests but fails 2 integration tests; additionally was rebased after a security patch. Context: ahead of the audit, while on-call rotation changed. Reported by the supervisor.
Rate release readiness for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_7f866e17d8147c30_n
noul
[ "false", "true" ]
[ 0.9, 0.1 ]
The release candidate deletes a deprecated API with 3 known consumers; additionally was rebased after a security patch. Context: ahead of the audit, during peak load. Reported by the monitoring system.
Is this scenario one where: this is safe to ship today?
software_delivery
technical
yuri_v3
v3_32457f6869cf5286_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0, 0, 0.12, 0.87, 0.01 ]
The migration pr passes unit tests but fails 2 integration tests; additionally shows a 9% regression in the p95 benchmark. Context: after a 3-week stabilization, during the system migration. Reported by the on-call engineer.
Rate regression risk for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_63e486b9fb8a1f17_n
noul
[ "false", "true" ]
[ 0.83, 0.17 ]
The release candidate was rebased after a security patch; additionally modifies the auth middleware. Context: after a 3-week stabilization, while legacy systems are still active. Reported by the on-call engineer.
Is this scenario one where: this is safe to ship today?
software_delivery
technical
yuri_v3
v3_15ef09f8f1f56231_c
choice
[ "smoke", "full_regression", "targeted_suite", "extended_soak" ]
[ 0.05, 0.44, 0.49, 0.02 ]
A hotfix build passes unit tests but fails 2 integration tests; additionally ships behind a feature flag at 5% traffic. Context: ahead of the audit, under reduced staffing. Reported by the review queue.
Test depth for this scenario.
software_delivery
technical
yuri_v3
v3_1e066227f5b1b8b5_c
choice
[ "smoke", "full_regression", "targeted_suite", "extended_soak" ]
[ 0.01, 0.84, 0.14, 0.01 ]
The migration pr changes 40% of the billing module; additionally has one blocking review comment unresolved. Context: in the payments repo, while on-call rotation changed. Reported by the monitoring system.
Test depth for this scenario.
software_delivery
technical
yuri_v3
v3_27e6ea194c56bafe_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0, 0, 0.2, 0.78, 0.02 ]
The migration pr introduces a new database index on a 2TB table; additionally adds a new dependency with no pinned hash. Context: for the 4.2 release, under reduced staffing. Reported by the on-call engineer.
Rate release readiness for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_fd46e7a559c77ff2_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0.01, 0.08, 0.2, 0.56, 0.14, 0.01 ]
A canary deploy ships behind a feature flag at 5% traffic; additionally is scheduled for the Friday freeze window. Context: after a 3-week stabilization, during an external partner integration. Reported by the on-call engineer.
Rate release readiness for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_6b4d2e0cb38b0a29_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0, 0, 0.14, 0.83, 0.03 ]
The release candidate adds a new dependency with no pinned hash; additionally shows a 9% regression in the p95 benchmark. Context: ahead of the audit, during peak load. Reported by the automated check.
Rate release readiness for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_e6fcaff43b54ea0e_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0.01, 0, 0.01, 0.25, 0.69, 0.04 ]
A hotfix build modifies the auth middleware; additionally introduces a new database index on a 2TB table. Context: for the 4.2 release, under reduced staffing. Reported by the automated check.
Rate release readiness for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_bd0b1cde44040228_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0, 0.02, 0.54, 0.44, 0 ]
The sdk release shows a 9% regression in the p95 benchmark; additionally changes 40% of the billing module. Context: after a 3-week stabilization, while on-call rotation changed. Reported by the on-call engineer.
Rate release readiness for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_2f44f4d09f93ece2_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0, 0.02, 0.71, 0.27, 0 ]
The release candidate shows a 9% regression in the p95 benchmark; additionally was rebased after a security patch. Context: in the payments repo, following a recent audit. Reported by the monitoring system.
Rate regression risk for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_4a0e9c7d7aee5595_c
choice
[ "ship", "ship_with_monitoring", "hold", "rollback" ]
[ 0, 0, 0.93, 0.07 ]
The sdk release adds a new dependency with no pinned hash; additionally deletes a deprecated API with 3 known consumers. Context: ahead of the audit, during peak load. Reported by the operator.
Go/no-go for this scenario.
software_delivery
technical
yuri_v3
v3_8f2c430ed37f0161_c
choice
[ "ship", "ship_with_monitoring", "hold", "rollback" ]
[ 0.02, 0.7, 0.27, 0.01 ]
The migration pr ships behind a feature flag at 5% traffic; additionally introduces a new database index on a 2TB table. Context: ahead of the audit, following a recent audit. Reported by the operator.
Go/no-go for this scenario.
software_delivery
technical
yuri_v3
v3_6b881c291eb3fc74_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0, 0, 0.06, 0.88, 0.06 ]
The release candidate has one blocking review comment unresolved; additionally changes 40% of the billing module. Context: for the 4.2 release, during a scheduled maintenance window. Reported by the supervisor.
Rate regression risk for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_1155006737d0278c_n
noul
[ "false", "true" ]
[ 0.8, 0.2 ]
The sdk release was rebased after a security patch; additionally passed the full canary matrix. Context: in the payments repo, under reduced staffing. Reported by the operator.
Is this scenario one where: the flag default is wrong?
software_delivery
technical
yuri_v3
v3_dac30e5f87528243_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0.02, 0.18, 0.3, 0.44, 0.05, 0.01 ]
The sdk release is scheduled for the Friday freeze window; additionally ships behind a feature flag at 5% traffic. Context: in the payments repo, shortly after a software update. Reported by the on-call engineer.
Rate release readiness for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_d17291e67e592c93_c
choice
[ "smoke", "full_regression", "targeted_suite", "extended_soak" ]
[ 0.17, 0.09, 0.74, 0 ]
A hotfix build is scheduled for the Friday freeze window; additionally modifies the auth middleware. Context: for the 4.2 release, under reduced staffing. Reported by the on-call engineer.
Test depth for this scenario.
software_delivery
technical
yuri_v3
v3_c9a0f0d6932dae33_n
noul
[ "false", "true" ]
[ 0.61, 0.39 ]
A hotfix build passed the full canary matrix; additionally is scheduled for the Friday freeze window. Context: for the 4.2 release, immediately after go-live. Reported by the automated check.
Is this scenario one where: this is safe to ship today?
software_delivery
technical
yuri_v3
v3_80c0395f1c6a725c_n
noul
[ "false", "true" ]
[ 0.91, 0.09 ]
A hotfix build modifies the auth middleware; additionally passes unit tests but fails 2 integration tests. Context: after a 3-week stabilization, during a scheduled maintenance window. Reported by the automated check.
Is this scenario one where: this is safe to ship today?
software_delivery
technical
yuri_v3
v3_4259760c547bb9fd_n
noul
[ "false", "true" ]
[ 0.81, 0.19 ]
The release candidate adds a new dependency with no pinned hash; additionally shows a 9% regression in the p95 benchmark. Context: ahead of the audit, immediately after go-live. Reported by the operator.
Is this scenario one where: the flag default is wrong?
software_delivery
technical
yuri_v3
v3_e6fcaff43b54ea0e_n
noul
[ "false", "true" ]
[ 0.87, 0.13 ]
A hotfix build modifies the auth middleware; additionally introduces a new database index on a 2TB table. Context: for the 4.2 release, under reduced staffing. Reported by the automated check.
Is this scenario one where: this is safe to ship today?
software_delivery
technical
yuri_v3
v3_e26e242f8fd88cec_c
choice
[ "smoke", "full_regression", "targeted_suite", "extended_soak" ]
[ 0.01, 0.26, 0.44, 0.29 ]
The migration pr was rebased after a security patch; additionally introduces a new database index on a 2TB table. Context: for the 4.2 release, during the morning shift. Reported by the operator.
Test depth for this scenario.
software_delivery
technical
yuri_v3
v3_faa18ec3ff51fba3_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0, 0, 0.01, 0.64, 0.35 ]
A hotfix build changes 40% of the billing module; additionally deletes a deprecated API with 3 known consumers. Context: in the payments repo, immediately after go-live. Reported by the on-call engineer.
Rate regression risk for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_10a7630f309cc89d_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0.01, 0.01, 0.07, 0.42, 0.47, 0.02 ]
The sdk release changes 40% of the billing module; additionally is scheduled for the Friday freeze window. Context: after a 3-week stabilization, as part of a compliance sweep. Reported by the review queue.
Rate release readiness for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_88b3bd55d4eb5f1e_c
choice
[ "smoke", "full_regression", "targeted_suite", "extended_soak" ]
[ 0.03, 0.57, 0.21, 0.19 ]
A canary deploy is scheduled for the Friday freeze window; additionally adds a new dependency with no pinned hash. Context: in the payments repo, during the holiday freeze. Reported by the on-call engineer.
Test depth for this scenario.
software_delivery
technical
yuri_v3
v3_35b57d7baaa49a36_n
noul
[ "false", "true" ]
[ 0.4, 0.6 ]
The release candidate ships behind a feature flag at 5% traffic; additionally passed the full canary matrix. Context: ahead of the audit, shortly after a software update. Reported by the operator.
Is this scenario one where: the change needs a second reviewer?
software_delivery
technical
yuri_v3
v3_ce0212c3dd355360_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0, 0.01, 0.34, 0.65, 0 ]
A canary deploy is scheduled for the Friday freeze window; additionally adds a new dependency with no pinned hash. Context: for the 4.2 release, during an external partner integration. Reported by the automated check.
Rate regression risk for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_7e0fdad08ac798de_c
choice
[ "ship", "ship_with_monitoring", "hold", "rollback" ]
[ 0, 0.14, 0.85, 0.01 ]
The release candidate modifies the auth middleware; additionally ships behind a feature flag at 5% traffic. Context: ahead of the audit, with staffing at reduced levels. Reported by the automated check.
Go/no-go for this scenario.
software_delivery
technical
yuri_v3
v3_3df028b2c8cedff2_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0.01, 0, 0.02, 0.27, 0.67, 0.03 ]
The migration pr has one blocking review comment unresolved; additionally is scheduled for the Friday freeze window. Context: ahead of the audit, during a scheduled maintenance window. Reported by the supervisor.
Rate release readiness for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_e312febb875dfb89_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0, 0.06, 0.34, 0.59, 0.01 ]
The release candidate has one blocking review comment unresolved; additionally modifies the auth middleware. Context: in the payments repo, at the end of the fiscal period. Reported by the review queue.
Rate release readiness for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_8bdeb79742882b58_n
noul
[ "false", "true" ]
[ 0.59, 0.41 ]
A canary deploy passed the full canary matrix; additionally deletes a deprecated API with 3 known consumers. Context: for the 4.2 release, while legacy systems are still active. Reported by the on-call engineer.
Is this scenario one where: the flag default is wrong?
software_delivery
technical
yuri_v3
v3_4fcfcd4a4bc6d1c7_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0, 0, 0.03, 0.87, 0.1 ]
A hotfix build adds a new dependency with no pinned hash; additionally changes 40% of the billing module. Context: in the payments repo, during an external partner integration. Reported by the operator.
Rate regression risk for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_2849e9964e6f3f17_c
choice
[ "smoke", "full_regression", "targeted_suite", "extended_soak" ]
[ 0.19, 0.04, 0.72, 0.05 ]
A canary deploy has one blocking review comment unresolved; additionally ships behind a feature flag at 5% traffic. Context: for the 4.2 release, during normal operations. Reported by the operator.
Test depth for this scenario.
software_delivery
technical
yuri_v3
v3_e7e1fe3b0386f5eb_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0.01, 0, 0.03, 0.3, 0.64, 0.02 ]
The migration pr changes 40% of the billing module; additionally modifies the auth middleware. Context: for the 4.2 release, under an active deadline. Reported by the review queue.
Rate release readiness for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_83a0316f09b27792_n
noul
[ "false", "true" ]
[ 0.84, 0.16 ]
A hotfix build introduces a new database index on a 2TB table; additionally changes 40% of the billing module. Context: for the 4.2 release, under reduced staffing. Reported by the on-call engineer.
Is this scenario one where: the flag default is wrong?
software_delivery
technical
yuri_v3
v3_d987b8679ab9c1e1_n
noul
[ "false", "true" ]
[ 0.18, 0.82 ]
A hotfix build adds a new dependency with no pinned hash; additionally ships behind a feature flag at 5% traffic. Context: for the 4.2 release, shortly after a software update. Reported by the automated check.
Is this scenario one where: the change needs a second reviewer?
software_delivery
technical
yuri_v3
v3_ae45e3925489ce9b_n
noul
[ "false", "true" ]
[ 0.95, 0.05 ]
The migration pr shows a 9% regression in the p95 benchmark; additionally passes unit tests but fails 2 integration tests. Context: ahead of the audit, under reduced staffing. Reported by the on-call engineer.
Is this scenario one where: this is safe to ship today?
software_delivery
technical
yuri_v3
v3_2b2842531538a773_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0.02, 0.36, 0.58, 0.04, 0 ]
The migration pr shows a 9% regression in the p95 benchmark; additionally passed the full canary matrix. Context: ahead of the audit, following a recent audit. Reported by the review queue.
Rate regression risk for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_a42a36be245cbaca_n
noul
[ "false", "true" ]
[ 0.83, 0.17 ]
The migration pr passes unit tests but fails 2 integration tests; additionally shows a 9% regression in the p95 benchmark. Context: ahead of the audit, during a scheduled maintenance window. Reported by the operator.
Is this scenario one where: the flag default is wrong?
software_delivery
technical
yuri_v3
v3_1c076829cb33b058_c
choice
[ "smoke", "full_regression", "targeted_suite", "extended_soak" ]
[ 0.05, 0.38, 0.39, 0.18 ]
A canary deploy is scheduled for the Friday freeze window; additionally adds a new dependency with no pinned hash. Context: after a 3-week stabilization, during the holiday freeze. Reported by the review queue.
Test depth for this scenario.
software_delivery
technical
yuri_v3
v3_c55518d9837933f3_c
choice
[ "smoke", "full_regression", "targeted_suite", "extended_soak" ]
[ 0.02, 0.42, 0.31, 0.25 ]
A hotfix build introduces a new database index on a 2TB table; additionally passed the full canary matrix. Context: in the payments repo, during a scheduled maintenance window. Reported by the supervisor.
Test depth for this scenario.
software_delivery
technical
yuri_v3
v3_af2fc56f252b4a4f_c
choice
[ "ship", "ship_with_monitoring", "hold", "rollback" ]
[ 0, 0.03, 0.5, 0.47 ]
The sdk release shows a 9% regression in the p95 benchmark; additionally modifies the auth middleware. Context: for the 4.2 release, immediately after go-live. Reported by the review queue.
Go/no-go for this scenario.
software_delivery
technical
yuri_v3
v3_dc67d4968f3fec0e_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0, 0.01, 0.45, 0.54, 0 ]
The sdk release was rebased after a security patch; additionally modifies the auth middleware. Context: for the 4.2 release, while legacy systems are still active. Reported by the monitoring system.
Rate regression risk for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_dcb2894bd0584dbd_c
choice
[ "smoke", "full_regression", "targeted_suite", "extended_soak" ]
[ 0.02, 0.59, 0.2, 0.19 ]
A hotfix build shows a 9% regression in the p95 benchmark; additionally introduces a new database index on a 2TB table. Context: for the 4.2 release, at the end of the fiscal period. Reported by the monitoring system.
Test depth for this scenario.
software_delivery
technical
yuri_v3
v3_83ee9e2b30da1eb5_c
choice
[ "smoke", "full_regression", "targeted_suite", "extended_soak" ]
[ 0.01, 0.65, 0.33, 0.01 ]
The sdk release has one blocking review comment unresolved; additionally deletes a deprecated API with 3 known consumers. Context: ahead of the audit, following a recent audit. Reported by the monitoring system.
Test depth for this scenario.
software_delivery
technical
yuri_v3
v3_ffbf42fcf7b3c69a_n
noul
[ "false", "true" ]
[ 0.81, 0.19 ]
A canary deploy was rebased after a security patch; additionally adds a new dependency with no pinned hash. Context: after a 3-week stabilization, immediately after go-live. Reported by the review queue.
Is this scenario one where: the flag default is wrong?
software_delivery
technical
yuri_v3
v3_5a119eb7cf69b7d7_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0, 0, 0.08, 0.88, 0.04 ]
The release candidate deletes a deprecated API with 3 known consumers; additionally shows a 9% regression in the p95 benchmark. Context: for the 4.2 release, during the holiday freeze. Reported by the on-call engineer.
Rate regression risk for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_69bfe501681889a1_n
noul
[ "false", "true" ]
[ 0.8, 0.2 ]
The release candidate modifies the auth middleware; additionally changes 40% of the billing module. Context: in the payments repo, during normal operations. Reported by the on-call engineer.
Is this scenario one where: the flag default is wrong?
software_delivery
technical
yuri_v3
v3_8a44510da3cbce5e_c
choice
[ "ship", "ship_with_monitoring", "hold", "rollback" ]
[ 0.01, 0.31, 0.62, 0.06 ]
The release candidate changes 40% of the billing module; additionally ships behind a feature flag at 5% traffic. Context: after a 3-week stabilization, immediately after go-live. Reported by the supervisor.
Go/no-go for this scenario.
software_delivery
technical
yuri_v3
v3_29ac45299100cc99_c
choice
[ "ship", "ship_with_monitoring", "hold", "rollback" ]
[ 0, 0.06, 0.5, 0.44 ]
A canary deploy changes 40% of the billing module; additionally shows a 9% regression in the p95 benchmark. Context: for the 4.2 release, during an external partner integration. Reported by the operator.
Go/no-go for this scenario.
software_delivery
technical
yuri_v3
v3_02224eb895a3874d_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0.02, 0.64, 0.32, 0.02, 0 ]
The migration pr passed the full canary matrix; additionally shows a 9% regression in the p95 benchmark. Context: in the payments repo, as part of a compliance sweep. Reported by the monitoring system.
Rate release readiness for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_0e348054ebf53f93_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0, 0, 0.06, 0.91, 0.03 ]
The migration pr has one blocking review comment unresolved; additionally deletes a deprecated API with 3 known consumers. Context: for the 4.2 release, under an active deadline. Reported by the supervisor.
Rate regression risk for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_ec9bdb2cb5571ff4_c
choice
[ "smoke", "full_regression", "targeted_suite", "extended_soak" ]
[ 0.02, 0.76, 0.21, 0.01 ]
The sdk release has one blocking review comment unresolved; additionally was rebased after a security patch. Context: ahead of the audit, at the end of the fiscal period. Reported by the supervisor.
Test depth for this scenario.
software_delivery
technical
yuri_v3
v3_6bd69c94dfd54719_n
noul
[ "false", "true" ]
[ 0.14, 0.86 ]
A hotfix build adds a new dependency with no pinned hash; additionally introduces a new database index on a 2TB table. Context: after a 3-week stabilization, while on-call rotation changed. Reported by the automated check.
Is this scenario one where: the change needs a second reviewer?
software_delivery
technical
yuri_v3
v3_c8f4156e52605f0c_n
noul
[ "false", "true" ]
[ 0.27, 0.73 ]
The release candidate deletes a deprecated API with 3 known consumers; additionally passed the full canary matrix. Context: after a 3-week stabilization, with staffing at reduced levels. Reported by the operator.
Is this scenario one where: the change needs a second reviewer?
software_delivery
technical
yuri_v3
v3_876a57f8219b1f8c_n
noul
[ "false", "true" ]
[ 0.77, 0.23 ]
The release candidate has one blocking review comment unresolved; additionally ships behind a feature flag at 5% traffic. Context: after a 3-week stabilization, during peak load. Reported by the operator.
Is this scenario one where: the flag default is wrong?
software_delivery
technical
yuri_v3
v3_b2f2a56155c42d96_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0, 0.04, 0.52, 0.43, 0.01 ]
The migration pr was rebased after a security patch; additionally changes 40% of the billing module. Context: for the 4.2 release, with a new vendor onboarded. Reported by the review queue.
Rate release readiness for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_474c66febfb186b5_c
choice
[ "ship", "ship_with_monitoring", "hold", "rollback" ]
[ 0.01, 0.39, 0.57, 0.03 ]
A hotfix build deletes a deprecated API with 3 known consumers; additionally ships behind a feature flag at 5% traffic. Context: for the 4.2 release, shortly after a software update. Reported by the supervisor.
Go/no-go for this scenario.
software_delivery
technical
yuri_v3
v3_2d7df4e2dce878f2_c
choice
[ "ship", "ship_with_monitoring", "hold", "rollback" ]
[ 0, 0.11, 0.88, 0.01 ]
The release candidate introduces a new database index on a 2TB table; additionally was rebased after a security patch. Context: in the payments repo, with staffing at reduced levels. Reported by the on-call engineer.
Go/no-go for this scenario.
software_delivery
technical
yuri_v3
v3_55786a8e8e185faf_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0.01, 0.05, 0.25, 0.28, 0.31, 0.1 ]
A canary deploy passed the full canary matrix; additionally changes 40% of the billing module. Context: in the payments repo, immediately after go-live. Reported by the automated check.
Rate release readiness for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_dc7585b9b77750fb_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0, 0.01, 0.15, 0.79, 0.05 ]
A canary deploy adds a new dependency with no pinned hash; additionally is scheduled for the Friday freeze window. Context: for the 4.2 release, with staffing at reduced levels. Reported by the monitoring system.
Rate release readiness for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_7c1caf3a2477a592_n
noul
[ "false", "true" ]
[ 0.72, 0.28 ]
A canary deploy is scheduled for the Friday freeze window; additionally was rebased after a security patch. Context: after a 3-week stabilization, under an active deadline. Reported by the automated check.
Is this scenario one where: the flag default is wrong?
software_delivery
technical
yuri_v3
v3_0a4a106c07cb9f3f_n
noul
[ "false", "true" ]
[ 0.95, 0.05 ]
The release candidate deletes a deprecated API with 3 known consumers; additionally changes 40% of the billing module. Context: after a 3-week stabilization, mid-incident. Reported by the automated check.
Is this scenario one where: this is safe to ship today?
software_delivery
technical
yuri_v3
v3_15664dabf74d29bd_c
choice
[ "ship", "ship_with_monitoring", "hold", "rollback" ]
[ 0.09, 0.56, 0.22, 0.13 ]
A hotfix build introduces a new database index on a 2TB table; additionally passed the full canary matrix. Context: in the payments repo, immediately after go-live. Reported by the operator.
Go/no-go for this scenario.
software_delivery
technical
yuri_v3
v3_0374d23da5e986f4_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0.01, 0, 0, 0.03, 0.65, 0.31 ]
The migration pr introduces a new database index on a 2TB table; additionally adds a new dependency with no pinned hash. Context: in the payments repo, mid-incident. Reported by the monitoring system.
Rate release readiness for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_9c389e15c18a7754_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0.01, 0, 0.01, 0.14, 0.77, 0.07 ]
A hotfix build changes 40% of the billing module; additionally deletes a deprecated API with 3 known consumers. Context: for the 4.2 release, under an active deadline. Reported by the monitoring system.
Rate release readiness for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_c6985cdbe49924da_n
noul
[ "false", "true" ]
[ 0.88, 0.12 ]
A canary deploy was rebased after a security patch; additionally shows a 9% regression in the p95 benchmark. Context: ahead of the audit, immediately after go-live. Reported by the review queue.
Is this scenario one where: this is safe to ship today?
software_delivery
technical
yuri_v3
v3_bd185db8d1f2680e_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0, 0.01, 0.28, 0.7, 0.01 ]
The migration pr changes 40% of the billing module; additionally shows a 9% regression in the p95 benchmark. Context: ahead of the audit, as part of a compliance sweep. Reported by the review queue.
Rate release readiness for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_2cb8f35ad0967122_n
noul
[ "false", "true" ]
[ 0.83, 0.17 ]
A hotfix build shows a 9% regression in the p95 benchmark; additionally deletes a deprecated API with 3 known consumers. Context: after a 3-week stabilization, shortly after a software update. Reported by the review queue.
Is this scenario one where: the flag default is wrong?
software_delivery
technical
yuri_v3
v3_bcfe6603eff015ce_n
noul
[ "false", "true" ]
[ 0.75, 0.25 ]
The sdk release changes 40% of the billing module; additionally ships behind a feature flag at 5% traffic. Context: in the payments repo, during the system migration. Reported by the automated check.
Is this scenario one where: the flag default is wrong?
software_delivery
technical
yuri_v3
v3_12826e83c1795045_n
noul
[ "false", "true" ]
[ 0.16, 0.84 ]
The migration pr deletes a deprecated API with 3 known consumers; additionally adds a new dependency with no pinned hash. Context: for the 4.2 release, with a new vendor onboarded. Reported by the operator.
Is this scenario one where: the change needs a second reviewer?
software_delivery
technical
yuri_v3
v3_43f8680e42a90522_c
choice
[ "smoke", "full_regression", "targeted_suite", "extended_soak" ]
[ 0.0505, 0.2828, 0.3838, 0.2828 ]
The sdk release ships behind a feature flag at 5% traffic; additionally passed the full canary matrix. Context: for the 4.2 release, while on-call rotation changed. Reported by the operator.
Test depth for this scenario.
software_delivery
technical
yuri_v3
v3_27304f3d56e248af_c
choice
[ "ship", "ship_with_monitoring", "hold", "rollback" ]
[ 0, 0.04, 0.95, 0.01 ]
The sdk release passed the full canary matrix; additionally adds a new dependency with no pinned hash. Context: ahead of the audit, at the end of the fiscal period. Reported by the automated check.
Go/no-go for this scenario.
software_delivery
technical
yuri_v3
v3_f9360e8ef2dae4f9_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0.01, 0.01, 0.03, 0.27, 0.65, 0.03 ]
The release candidate deletes a deprecated API with 3 known consumers; additionally is scheduled for the Friday freeze window. Context: ahead of the audit, with a new vendor onboarded. Reported by the supervisor.
Rate release readiness for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_4e80c3c6ccf438b1_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0.01, 0, 0.01, 0.24, 0.71, 0.03 ]
The release candidate was rebased after a security patch; additionally deletes a deprecated API with 3 known consumers. Context: ahead of the audit, under an active deadline. Reported by the monitoring system.
Rate release readiness for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_076b7c48f23a1899_n
noul
[ "false", "true" ]
[ 0.85, 0.15 ]
A hotfix build was rebased after a security patch; additionally deletes a deprecated API with 3 known consumers. Context: ahead of the audit, during peak load. Reported by the supervisor.
Is this scenario one where: the flag default is wrong?
software_delivery
technical
yuri_v3
v3_223f99c5709d6706_n
noul
[ "false", "true" ]
[ 0.09, 0.91 ]
A hotfix build modifies the auth middleware; additionally adds a new dependency with no pinned hash. Context: after a 3-week stabilization, under reduced staffing. Reported by the operator.
Is this scenario one where: the change needs a second reviewer?
software_delivery
technical
yuri_v3
v3_c4e12e3318258db4_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0, 0.04, 0.56, 0.4, 0 ]
A canary deploy introduces a new database index on a 2TB table; additionally passes unit tests but fails 2 integration tests. Context: after a 3-week stabilization, as part of a compliance sweep. Reported by the operator.
Rate regression risk for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_7a6e3c229349fc4c_n
noul
[ "false", "true" ]
[ 0.87, 0.13 ]
The sdk release passes unit tests but fails 2 integration tests; additionally has one blocking review comment unresolved. Context: for the 4.2 release, during the quarterly review. Reported by the on-call engineer.
Is this scenario one where: the flag default is wrong?
software_delivery
technical
yuri_v3
v3_618062baae202a4c_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0.01, 0.39, 0.55, 0.05, 0 ]
The migration pr shows a 9% regression in the p95 benchmark; additionally passed the full canary matrix. Context: after a 3-week stabilization, while legacy systems are still active. Reported by the on-call engineer.
Rate release readiness for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_7e9f30aed1d37991_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0.01, 0.31, 0.61, 0.07, 0 ]
A canary deploy shows a 9% regression in the p95 benchmark; additionally ships behind a feature flag at 5% traffic. Context: after a 3-week stabilization, during the quarterly review. Reported by the automated check.
Rate release readiness for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_3efa62d5c8a789c5_c
choice
[ "smoke", "full_regression", "targeted_suite", "extended_soak" ]
[ 0.01, 0.81, 0.15, 0.03 ]
The sdk release passed the full canary matrix; additionally changes 40% of the billing module. Context: ahead of the audit, during the morning shift. Reported by the supervisor.
Test depth for this scenario.
software_delivery
technical
yuri_v3
v3_1d0c723c339c9ea5_n
noul
[ "false", "true" ]
[ 0.3, 0.7 ]
A canary deploy ships behind a feature flag at 5% traffic; additionally has one blocking review comment unresolved. Context: in the payments repo, while on-call rotation changed. Reported by the operator.
Is this scenario one where: the change needs a second reviewer?
software_delivery
technical
yuri_v3
v3_bb5f51d08ed8f2a1_n
noul
[ "false", "true" ]
[ 0.94, 0.06 ]
The sdk release adds a new dependency with no pinned hash; additionally passes unit tests but fails 2 integration tests. Context: for the 4.2 release, while legacy systems are still active. Reported by the operator.
Is this scenario one where: this is safe to ship today?
software_delivery
technical
yuri_v3
v3_ade9a971d05f0e14_c
choice
[ "smoke", "full_regression", "targeted_suite", "extended_soak" ]
[ 0, 0.7, 0.17, 0.13 ]
The migration pr changes 40% of the billing module; additionally ships behind a feature flag at 5% traffic. Context: ahead of the audit, during the quarterly review. Reported by the review queue.
Test depth for this scenario.
software_delivery
technical
yuri_v3
v3_60e0ef0c1c43d288_n
noul
[ "false", "true" ]
[ 0.14, 0.86 ]
A canary deploy deletes a deprecated API with 3 known consumers; additionally introduces a new database index on a 2TB table. Context: in the payments repo, immediately after go-live. Reported by the review queue.
Is this scenario one where: the change needs a second reviewer?
software_delivery
technical
yuri_v3
v3_0465351d1828f127_n
noul
[ "false", "true" ]
[ 0.8, 0.2 ]
A canary deploy passed the full canary matrix; additionally modifies the auth middleware. Context: after a 3-week stabilization, during normal operations. Reported by the automated check.
Is this scenario one where: the flag default is wrong?
software_delivery
technical
yuri_v3
v3_972ce7eb9fc64f5d_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0.01, 0, 0, 0.08, 0.86, 0.05 ]
The migration pr passes unit tests but fails 2 integration tests; additionally shows a 9% regression in the p95 benchmark. Context: in the payments repo, under reduced staffing. Reported by the review queue.
Rate release readiness for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_06fa2e35cf360feb_c
choice
[ "smoke", "full_regression", "targeted_suite", "extended_soak" ]
[ 0.02, 0.49, 0.38, 0.11 ]
A canary deploy passes unit tests but fails 2 integration tests; additionally introduces a new database index on a 2TB table. Context: ahead of the audit, while legacy systems are still active. Reported by the on-call engineer.
Test depth for this scenario.
software_delivery
technical
yuri_v3
v3_0215ffca5938646d_c
choice
[ "ship", "ship_with_monitoring", "hold", "rollback" ]
[ 0.01, 0.05, 0.88, 0.06 ]
The migration pr adds a new dependency with no pinned hash; additionally passed the full canary matrix. Context: after a 3-week stabilization, during a scheduled maintenance window. Reported by the monitoring system.
Go/no-go for this scenario.
software_delivery
technical
yuri_v3
v3_9ce6021c2bbb4e3f_c
choice
[ "ship", "ship_with_monitoring", "hold", "rollback" ]
[ 0, 0, 0.99, 0.01 ]
A hotfix build passes unit tests but fails 2 integration tests; additionally adds a new dependency with no pinned hash. Context: for the 4.2 release, during a scheduled maintenance window. Reported by the on-call engineer.
Go/no-go for this scenario.
software_delivery
technical
yuri_v3
v3_ed92c5824badc0a2_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0.01, 0.06, 0.6, 0.32, 0.01 ]
The migration pr is scheduled for the Friday freeze window; additionally was rebased after a security patch. Context: after a 3-week stabilization, at the end of the fiscal period. Reported by the operator.
Rate regression risk for this scenario on a 0-5 scale.
software_delivery
technical
yuri_v3
v3_7a492a47050cb38c_c
choice
[ "smoke", "full_regression", "targeted_suite", "extended_soak" ]
[ 0.04, 0.34, 0.34, 0.28 ]
A canary deploy ships behind a feature flag at 5% traffic; additionally shows a 9% regression in the p95 benchmark. Context: for the 4.2 release, shortly after a software update. Reported by the operator.
Test depth for this scenario.
software_delivery
technical
yuri_v3