yahoo-eng-team team mailing list archive

[Brian Rosmaita <rosmaita.fossdev@xxxxxxxxx>]

Public bug reported:

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.

** Affects: glance
     Importance: Medium
         Status: Triaged

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1812856

Title:
  DB migration code will break after 'z' release

Status in Glance:
  Triaged

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1812856/+subscriptions