By contributing, you agree that your contributions will be licensed under the projects original open source license.
Description
This was originally put into place to stop upgrades early on if the source version was an unsupported upgrade. A problem with this design was exposed VBR 10a as it was released as a full ISO vs a patch file.
A full ISO uses the upgrade process to apply updates so we can no longer assume that upgrades will occur from the previous version of the product.
To resolve this behavior, I'm removing the source version verification checks. This should not be an issue as the software upgrade itself has these checks built-in.
Type of change
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
How Has This Been Tested?
Code has been tested in my lab.
Checklist (check all applicable):
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard to understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
Pull Request Template
By contributing, you agree that your contributions will be licensed under the projects original open source license.
Description
This was originally put into place to stop upgrades early on if the source version was an unsupported upgrade. A problem with this design was exposed VBR 10a as it was released as a full ISO vs a patch file.
A full ISO uses the upgrade process to apply updates so we can no longer assume that upgrades will occur from the previous version of the product.
To resolve this behavior, I'm removing the source version verification checks. This should not be an issue as the software upgrade itself has these checks built-in.
Type of change
How Has This Been Tested?
Code has been tested in my lab.
Checklist (check all applicable):