DB migration code will break after 'z' release

[Brian Rosmaita]

According to https://governance.openstack.org/tc/reference/release-naming.html the next release after 'z' will be 'a'. Some of our tooling for database migrations orders the scripts alphabetically, which seemed a great idea when we did it back in Ocata, but is looking problematic as we approach the end of the alphabet.

Specifically, I'm thinking of glance/db/sqlalchemy/alembic_migrations/data_migrations/__init__.py but there may be other places in the code.

I have no idea what's the best approach to fix this, just wanted to file the bug so we remember to do something about it during (or before) the Z cycle.

[Cyril Roelandt (cyril-roelandt)]

I'm not sure when we fixed this, but we probably fixed it since we're releasing Epoxy these days :)