I have tested it with a practice 2.9.6 build. It produces an upgrade script that does the bare minimum of inserting the version into config.upgrade_log when there are no db upgrades.
I also made a custom, 2.8.8 to 2.9.6 upgrade tarball and that one had commands in the upgrade script, so it still works when there are db upgrades to do.
I have pushed a working branch based on master to working/ user/dyrcona/ lp1583608- make_release- always- db-upgrade.
http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ dyrcona/ lp1583608- make_release- always- db-upgrade
I have tested it with a practice 2.9.6 build. It produces an upgrade script that does the bare minimum of inserting the version into config.upgrade_log when there are no db upgrades.
I also made a custom, 2.8.8 to 2.9.6 upgrade tarball and that one had commands in the upgrade script, so it still works when there are db upgrades to do.