Currently, because is not easily upgradable/downgradable.
For example, we don't have an easy way to change and rollback schema changes.
Perhaps something like sqlalchemy-migrate could be used for this.
At this stage alembic is probably the project we want to use for this (rather than sqlalchemy-migrate):
I also wrote an automated test for the migration process:
and back-populated the migrations to 0.12:
plus fixed a few random bugs in the existing migrations that shook out from the tests.
... and one more, to eliminate the manual stamping step on first upgrade. beaker-init will guess the right version by checking for certain tables/columns.
(In reply to Dan Callaghan from comment #5)
> ... and one more, to eliminate the manual stamping step on first upgrade.
> beaker-init will guess the right version by checking for certain
I discovered a problem with this patch, it doesn't correctly stamp the db after guessing the version.
Beaker 19.0 has been released.