[PDB-3993] Add --upgrade-and-quit or similar for unattended multi-version upgrades Created: 2018/07/30 Updated: 2018/10/22 Resolved: 2018/09/06
|Fix Version/s:||PDB 5.2.6, PDB 6.0.0|
|Reporter:||Rob Browning||Assignee:||Rob Browning|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|Release Notes:||New Feature|
|Release Notes Summary:|| (Note: this feature was added to 5.2.x and to 6.0.0, so we have two sets of release notes depicted below. The 5.2.x notes should go on the 5.2.x branch, and then we'll merge them up to master (or 6.0.x), and then
the 6.0 notes should be added to master (or 6.0.x).)
*** For 6.0.0 ***
- A `help` subcommand has been added to display usage information to standard output.
- If an invalid command is specified, usage information will now be printed to standard error, not standard output.
*** For 5.2.x ***
### New features
- An `upgrade` subcommand has been added that should be useful for cases where you want to upgrade across multiple major versions without skipping major versions (as per the [versioning policy][versioning]). See [these notes [multiple-major-upgrades] for additional information.
|QA Risk Assessment:||Needs Assessment|
So that someone on a much older version of pdb can just run the updates in sequence without having to try to guess when an upgrade is complete.