V2.0 migration plan

[Jaymassena]

Here is our current rough idea of how this will happen:

• Write a migration script that copies and transforms data from the V1 database to the V2 database. (See issue V2.0 migration script #441)
• Write communication to existing users about the changes in Patchr 2.0. Warn them that once Patchr 2.0 is available, version 1.0 will be turned off and they will be required to update to 2.0 to continue using the Patchr service.
• Release Patchr 2.0 clients.
• Force client updates using minimum client version from the V1 service.
• Migrate data from V1 to V2.

Supporting a more gradual transition from V1 to V2 would require a single user migration script that would be executed on first-run of a V2 client.

[georgesnelling]

Closing in favor of Issue #445