Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1665
@jburwell -1
The db upgrade version only considers the major/minor fields such as a.b.c,
the last `.d` is ignored (for that matter any other suffix in the version). Due
to the current mechanism of how db versions are implemented, used and run, the
change cannot be accepted as it will cause db upgrade failures when the upgrade
path is run (as you can see Travis has failed all jobs at the deploydb step).
The db upgrade paths therefore won't run for any security release (for example,
b/w 4.9.1.0 and 4.9.1.1), unless we want to have db changes between security
releases for the same major.minor release?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
