[SERVER-60873] Rename multiversion-setup to setup-repro-env Created: 21/Oct/21 Updated: 06/Dec/22 Resolved: 10/Dec/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Robert Guo (Inactive) | Assignee: | Backlog - Server Tooling and Methods (STM) (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | dp-qp-stakeholder-request-2021-10 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Server Tooling & Methods
|
||||||||||||
| Participants: | |||||||||||||
| Story Points: | 2 | ||||||||||||
| Description |
|
The multiversion setup script should be renamed to better convey its functionality and be more intuitive. Update the name in:
|
| Comments |
| Comment by Andrew Morrow (Inactive) [ 26/Oct/21 ] |
|
brooke.miller - I think that sounds quite a bit better. Thanks... |
| Comment by Brooke Miller [ 26/Oct/21 ] |
|
How does setup-repro-env sound, acm? |
| Comment by Andrew Morrow (Inactive) [ 26/Oct/21 ] |
|
I guess I just don't see that as a "dev" environment. To me, a dev environment is the stuff you need in order to author changes to the product. This still feels like it is about reproducing test failures. Can we bikeshed a different name? |
| Comment by Robert Guo (Inactive) [ 22/Oct/21 ] |
|
acm the script does the following: |