[SERVER-33271] Move generic upgrade/downgrade tests into multiVersion/generic directory Created: 12/Feb/18 Updated: 29/Oct/23 Resolved: 23/Jul/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Upgrade/Downgrade |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.2 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Maria van Keulen | Assignee: | Dewal Gupta |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Storage NYC 2018-07-02, Storage NYC 2018-07-16, Storage NYC 2018-07-30 |
| Participants: |
| Description |
|
This organizational change allows developers to specify whether their upgrade/downgrade testing is generic (i.e., it can be kept from release to release) or specific to a particular release. Upgrade/downgrade testing that is not included in this "generic" directory will be assumed to be specific to a particular release. |
| Comments |
| Comment by Githook User [ 20/Jul/18 ] |
|
Author: {'username': 'dewalg', 'name': 'Dewal Gupta', 'email': 'dewal.gupta@10gen.com'}Message: |