-
Type:
Task
-
Resolution: Done
-
Priority:
Minor - P4
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
Fully Compatible
-
v3.4
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Using 'legacy' in task names / suite names leads to ambiguity about whether legacy refers to PV0, SCCC, legacy read mode, legacy write ops, or something else entirely.
We should update these suite names for clarity:
| Current name | Proposed name |
|---|---|
| replicasets_legacy | replicasets_pv0 |
| sharding_legacy | sharding_sccc |
| sharding_legacy_multiversion | sharding_sccc_multiversion |
| sharding_legacy_op_query_WT | sharding_sccc_read_mode_legacy_WT |
| sharding_op_query_WT | sharding_read_mode_legacy_WT |
- related to
-
SERVER-27995 Make replication naming conventions consistent
-
- Closed
-