Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Done
Priority: Minor - P4
Fix Version/s: 3.4.3, 3.5.4
Affects Version/s: None
Component/s: Testing Infrastructure
Labels:
- tig-evgconfig

Backwards Compatibility:
Fully Compatible
Backport Requested:

v3.4
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
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

Assignee:: Judah Schvimer
Reporter:: Kamran K. (Inactive)
Participants:: Githook User, Judah Schvimer, Kamran K.
Votes:: 0 Vote for this issue
Watchers:: 6 Start watching this issue

Created:: Nov 25 2015 07:36:05 PM UTC
Updated:: Apr 05 2017 11:44:39 AM UTC
Resolved:: Feb 28 2017 03:29:32 PM UTC
Confidence Status Last Update:: 22/Feb/17 9:25 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates