1606: Explicitly document which versions are database-compatible

mate.******@gmai***** (Google Code) (Is this you? Claim this profile.)
Oct. 8, 2011 
What's the URL of the page containing the problem?

http://www.reviewboard.org/docs/manual/dev/admin/installation/development-releases/

Describe the problem and any recommendations below.

It says:
"Note that if you install an in-development/nightly build, you may not be
able to downgrade back to a stable build, due to database changes. Be
careful when running on production servers, and always back up your database."

Could you please be more explicit? The most important topic is downgrading.

It would help if it were made clear which versions can be downgraded to
which versions.

Can I always downgrade a nightly to the latest dev release? Can I downgrade
1.1alpha3 to 1.1alpha2? Can I always downgrade between two different
"beta2" snapshots?

And an important question: What happens if I downgrade the binaries (with
easy_install) to a database-incompatible version? How will I notice? What
will "rb-site upgrade" do?
david
#1 david 
This is not something that we're really capable of doing (especially in the downgrade case). We try not to make schema changes too often, but generally if you had to run an evolution to upgrade, you won't be able to downgrade. When you throw nightlies and betas into the mix, the number of combinations we'd have to document is enormous.
  • +WontFix