[SERVER-21675] Remove 'legacy' from Evergreen task names Created: 25/Nov/15 Updated: 05/Apr/17 Resolved: 28/Feb/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.3, 3.5.4 |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Kamran K. | Assignee: | Judah Schvimer |
| Resolution: | Done | Votes: | 0 |
| Labels: | tig-evgconfig | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v3.4
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
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:
|
| Comments |
| Comment by Githook User [ 06/Mar/17 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: (cherry picked from commit f17d826a61b01023f6034bc62138639c2d704311) |
| Comment by Githook User [ 28/Feb/17 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: |