Created by: mkszuba
Bump the API and the schema version to 99. Patch the test databases accordingly (includes the master-branch equivalent of #397. Tell Travis to have the Registry shut up about version mismatches between the API and the databases so that we can still get meaningful test results in spite of Compara, Variation and ontology database schemas remaining at 98.
According to the revised Core release SOP we want to do N+1 version bumps right after branching release/N. For the current release cycle, the relevant Jira ticket is ENSCORESW-3163.
Early version bumping will make it clear that what we have on the master branch is not necessarily the same API/schema as on even the latest release branch. Moreover, it will give us more time to catch and address possible issues with release 100.
The code-branching step if the release schedule will be slightly more complicated because it will be necessary to reenable version-mismatch warnings in .travis.yml before pushing a new release branch.
Have you added/modified unit tests to test the changes?
If so, do the tests pass/fail?
Have you run the entire test suite and no regression was detected?
Have run the entire test suite with version-mismatch warnings both enabled and disabled. In the former case ontologyTerm.t and sequenceOntologyMapper.t fail due to having produced unexpected warnings, in the latter case everything works.